Method to achieve bounded buffer sizes and quality of service guarantees in the internet network

ABSTRACT

Methods to achieve bounded router buffer sizes and Quality of Service guarantees for traffic flows in a packet-switched network are described. The network can be an Internet Protocol (IP) network, a Differentiated Services network, an MPLS network, wireless mesh network or an optical network. The routers can use input queueing, possibly in combination with crosspoint queueing and/or output queueing. Routers may schedule QoS-enabled traffic flows to ensure a bounded normalized service lead/lag. Each QoS-enabled traffic flow will buffer O(K) packets per router, where K is an integer bound on the normalized service lead/lag. Three flow-scheduling methods are analysed. Non-work-conserving flow-scheduling methods can guarantee a bound on the normalized service lead/lag, while work-conserving flow-scheduling methods typically cannot guarantee the same small bound. The amount of buffering required in a router can be reduced significantly, the network links can operate near peak capacity, and strict QoS guarantees can be achieved.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.14/792,226 filed on Jul. 6, 2015, which is a continuation of U.S.application Ser. No. 14/093,874 filed on Dec. 2, 2013, which is acontinuation of U.S. application Ser. No. 13/074,834 filed on Mar. 29,2011, which claims priority from the benefit of the filing date of U.S.Provisional Application No. 61/318,663 filed on Mar. 29, 2010, entitled“METHOD TO ACHIEVE BOUNDED BUFFER SIZES AND QUALITY OF SERVICEGUARANTEES IN THE INTERNET NETWORK”; the contents of which are herebyincorporated by reference.

FIELD OF THE INVENTION

The present invention relates generally to communications networks,devices and methods, and more particularly to methods to achieve boundedbuffer sizes and mathematically provable Quality of Service (QoS)guarantees in packet switched networks, including the Internet Protocol(IP) network, ATM networks, MPLS networks, optical networks and wirelessmesh networks. These bounds and strict QoS guarantees hold even when thenetwork is operated at 100% of capacity.

BACKGROUND OF THE INVENTION Articles Incorporated by Reference

The following documents are hereby incorporated by reference. Thesedocuments may be referred to by their title or by their numeric value.

-   [1] A. K. Parekh and R. G. Gallager, “A Generalized Processor    Sharing Approach to Flow Control in Integrated Service Networks: the    Single Node Case”, IEEE/ACM Trans. Networking, vol. 1, pp. 344-357,    1993.-   [2] A. K. Parekh and R. G. Gallager, “A Generalized Processor    Sharing Approach to Flow Control in Integrated Service Networks: the    Multiple Node Case”, IEEE/ACM Trans. Networking, vol. 2, no. 2, pp.    137-150, 1994.-   [3] A. Leon-Garcia and I. Widjaja, “Communication Networks,    Fundamental Concepts and Key Architectures”, second Edition, McGraw    Hill, 2004.-   [4] US patent, J. W. Marshal et al, “Supplemental queue sampling    technique for packet scheduling”, U.S. Pat. No. 7,640,355, December    2009.-   [5] L. G. Roberts, “A Radical New Router”, IEEE Spectrum, July 2009.-   [6] C. E Koksal, R. G. Gallager, C. E. Rohrs, “Rate Quantization and    Service Quality over Single Crossbar Switches”, IEEE Infocom    Conference, 2004.-   [7] I. Keslassy, M. Kodialam, T. V. Lakshman and D. Stiliadis, “On    Guaranteed Smooth Scheduling for Input-Queued Switches”, IEEE/ACM    Trans. Networking, Vol. 13, No. 6, December 2005.-   [8] W. J. Chen, C-S. Chang, and H-Y. Huang, “Birkhoff-von Neumann    Input Buffered Crossbar Switches for Guaranteed-Rate Services”, IEEE    Trans. Comm., Vol. 49, No. 7, July 2001, pp. 1145-1147.-   [9] S. R. Mohanty and L. N. Bhuyan, “Guaranteed Smooth Switch    Scheduling with Low Complexity”, IEEE Globecom Conference, 2005, pp.    626-630-   [10] S. Iyer, R R. Kompella, N. Mckeown, “Designing Packet Buffers    for Router Linecards”, IEEE Trans. Networking, Vol. 16, No. 3, June    2008, pp. 705-717-   [11] R. S. Prasas, C. Dovrolis, M. Thottan, “Router Buffer Sizing    for TCP Traffic and the Role of the Output/Input Capacity Ratio”,    IEEE Trans. Networking, 2009.-   [12] Y. Ganjali, N, McKeown, “Update on Buffer Sizing in Internet    Routers”, ACM Sigcomm Comp. Comm. Rev., pp. 67-70, October 2006.-   [13] G. Appenzeller, I. Keslassy and N. McKeown, “Sizing router    buffers”, ACM Sigcomm Comp. Comm. Rev., USA, pp. 281-292, 2004.-   [14] G. Raina and D. Wishick, “Buffer sizes for large multiplexers:    TCP queueing theory and instability analysis”, EuroNGI, Italy, April    2005.-   [15] M. Enachescu, Y. Ganjali, A. Goel, N. McKeown, T. Roughgarden,    “Routers with very small buffers”, IEEE Infocom Conference, Spain,    April 2006.-   [16] A. Dhamdhere and C. Dovrolis, “Open Issues in Router Buffer    Sizing”, ACM/SIGCOMM Comp. Comm. Rev., vol. 36, no. 1, pp. 87-92,    January 2006.-   [17] G. Vu-Brugier, R. S. Stanojevic, D. J. Leith, and R. N.    Shorten, “A Critique of recently proposed buffer sizing strategies”,    ACM/SIGCOMM Comp. Comm. Rev., vol. 37, no. 1, pp. 43-47, May 2007.-   [18] T. H. Szymanski, “A Low-Jitter Guaranteed Rate Scheduling    Algorithm for Packet-Switched IP Routers”, IEEE Trans.    Communications., Vol. 57, No. 11, November 2009, pp. 3446-3450.-   [19] T. H. Szymanski, “Bounds on the End-to-End Delay and Jitter in    Input-Buffered and Internally Buffered IP Networks”, IEEE Sarnoff    Symposium, Princeton, N.J., April 2009.-   [20] T. H. Szymanski and D. Gilbert, “Internet Multicasting of IPTV    with Essentially-Zero Delay Jitter”, IEEE Trans. Broadcasting, Vol.    55, No. 1, March 2009, pp. 20-30.-   [21] T. H. Szymanski and D. Gilbert, “Provisioning Mission-Critical    Telerobotic Control Systems over Internet Backbone Networks with    Essentially-Perfect QoS”, IEEE JSAC, Vol. 28, No. 5, June 2010.-   [22] T. H. Szymanski, “Scheduling of Backhaul Traffic Flows in    TDMA/ODFMA Infrastructure Wireless Mesh Networks with Near-Perfect    QoS”, IEEE 2010 Sarnoff Symposium, Princeton University, N.J., April    2010.-   [23] T. H. Szymanski, “A Low-Jitter Guaranteed-Rate Scheduling    Algorithm for Crosspoint Buffered Switches”, IEEE 2009 Pacific Rim    Conference on Computers, Communications and Signal Processing,    August 2009, Victoria BC.-   [24] T. H. Szymanski, “Conflict-Free Low-Jitter Guaranteed-Rate MAC    Protocol for Base-Station Communications in Wireless Mesh Networks”,    2008 Int, Conf. on Access Networks (ACCESSNETS-08), Las Vegas,    October 2008. Also in Springer ACCESSNETS—Lectures Notes in Computer    Science LNICST 6, 2009, pp. 118-137.-   [25] T. H. Szymanski, “Bounds on Memory Requirements in Internet    Routers”, submitted, IEEE Globecom conference, 2010.-   [26] D. Bertsekas and R. Gallager, ‘Data Networks”, 2nd edition,    Prentice Hall.

Background of the Invention—Continued

The closely-related issues of buffer sizing and QoS guarantees in theInternet network have been studied extensively in the literature.Unfortunately, to date the there are no proven techniques to achievesmall and bounded buffer sizes in Internet network routers, except for aspecial case of ideal output queued routers using the Weighted FairQueueing scheduling algorithm. To date there are no techniques toachieve strict guarantees on the Quality of Service (QoS) for multipletraffic flows or multiple classes of traffic flows in the Internetnetwork, except for a special case of ideal output queued routers usingthe Weighted Fair Queueing scheduling algorithm. To date there are noproven techniques to enable practical networks to operate at essentially100% of their capacity, while maintaining small and bounded buffer sizesin the routers and meeting strict QoS guarantees.

The Generalized Processor Sharing/Weighted Fair Queueing (GPS/WFQ)scheduling algorithm is described in the paper [1] by A. K. Parekh andR. G. Gallager, entitled “A Generalized Processor Sharing Approach toFlow Control in Integrated Service Networks: the Single Node Case”,IEEE/ACM Trans. Networking, 1993. The GPS/WFQ method is also describedin the paper [2] by A. K. Parekh and R. G. Gallager, entitled “AGeneralized Processor Sharing Approach to Flow Control in IntegratedService Networks: the Multiple Node Case”, IEEE/ACM Trans. Networking,1994.

Recently, the original designers of the Internet have argued that TheInternet is Broken, i.e., the current Internet routers are too slow,they consume too much power, and they offer poor QoS [5]. The followingquote from [5] illustrates the problem:

-   -   “(users) enjoy those services only because the Internet has been        grossly over-provisioned. Network operators have deployed        mountains of optical communication systems that can handle        traffic spikes, but on average these run much below their full        capacity . . . . So although users may not perceive the extent        of the problem, things are already dire for many Internet        service providers and network operators. Keeping up with        bandwidth demand has required huge outlays of cash to build an        infrastructure that remains underutilized. To put it another        way, we've thrown bandwidth at a problem that really requires a        computing solution.”

Over the last few years, the issue of buffer sizing in IP routers hasbeen debated in the ACM Computer Communications Review [11]. A classicdesign rule called the ‘Bandwidth-Delay Product rule’ states that eachlink in each IP router requires a buffer of B=O(C*T) bits, where C isthe link capacity and T is the round-trip time of the flows traversingthe link [15]. According to data in [15], a 40 Gbps link handling TCPflows with a round-trip time of 250 millisec requires a buffer size B ofabout one million IP packets. In practice, IP packets may contain up to1,500 bytes, and therefore a buffer for a 40 Gbps link may requireseveral Gigabytes of expensive high-speed memory, which consumessignificant power.

A ‘small buffer rule’ was proposed in [15], where B=O(CT/N̂(½)) and whereN is the number of long-lived TCP flows traversing the router. With thesame parameters reported above, the buffer size B is reduced to aboutfifty thousand IP packets [15]. [15] also proposed a ‘Tiny Buffer rule’where B=O(log W), where W is the maximum TCP congestion window size.With the same parameters, it was postulated that average buffer sizes ofbetween 20-50 IP packets or equivalently about 30K-75K bytes of memorymay suffice if 3 conditions can be met; (a) the jitter of incomingtraffic at the source node is sufficiently small, (b) the IP routersintroduce a sufficiently small jitter, and (c) 10-20% of the currentthroughput is sacrificed. The paper [15] however did not propose alow-jitter scheduling algorithm, which was in itself a major theoreticalunsolved problem. Furthermore, [16,17] have argued that small buffersmay cause significant losses, instability or performance degradation atthe application layer.

There are a number of problems with the small buffer rule in [15].First, the buffers can be quite large, and there is no proof that thebuffer sizes are bounded. Without any strict upper bounds on buffersizes, a manufacturer of routers will have to build routers withunnecessarily large buffers, to handle the worst-cases buffer sizes thatmay be encountered. Second, the small-buffer rule does not offer anystrict Quality of Service guarantees for any traffic flows. It does notaddress the Quality of Service problem. Third, it offers no solution tothe fact that current networks are over-provisioned to achievereasonable QoS. In other words, it does not offer any means to operatenetworks at nearly 100% of their capacity and achieve QoS guarantees.Current Internet links operate at a small fraction of their peakcapacity. Finally, it does not propose a low-jitter scheduling algorithmfor the switches or routers, which has been a major theoretical unsolvedproblem in the literature for several years.

Many new services are being developed for the Internet. New servicessuch as telerobotically-assisted surgery require that a surgeon at onelocation controls a medical robot at a remote location over a network.Such new services may present a risk to human lives if the networkcannot provide strict QoS guarantees. Therefore these new services willrequire strict QoS guarantees which existing Internet networks cannotprovide.

A quote from a recent 2009 journal article on buffer-sizing [11] furtherillustrates the problem:

-   -   “the basic question—how much buffering do we need at a given        router interface?—has received hugely different answers in the        last 15 to 20 years, such as ‘a few dozens of packets’, ‘a        bandwidth-delay product’, or ‘a multiple of the number of large        TCP flows in that link.’ It cannot be that all these answers are        right. It is clear that we are still missing a crucial piece of        understanding despite the apparent simplicity of the previous        question.”

In summary, today's Internet routers are based on complex designs, theyare large, costly and consume great deals of power. They are basedlargely in heuristic algorithms for scheduling. As a result, they cannotprovide any strict QoS guarantees, they cannot operate at 100% ofcapacity, and they rely upon significant over-provisioning to providereasonable Quality of Service. The current Internet functions becausethe backbone networks have been significantly over-provisioned, toaccommodate spikes in traffic.

It has recently been estimated that the inefficient use of Internetresources such as link bandwidth and router buffers results in excessoperating costs of several hundred million dollars per year. It has alsobeen estimated that the Internet is contributing a noticable percentageof all worldwide greenhouse gasses, thereby contributing to GlobalWarming and Climate Change.

In this paper, we present methods to achieve strict (i.e.,mathematically provable) bounds on router buffer sizes and guaranteesfor the QoS of provisioned traffic flows in a packet switched network. Aprovisioned traffic flow is assigned to one or more paths through thenetwork, where sufficient bandwidth has been allocated (provisioned) forthe flow on each link in each path(s). The bounds on the router buffersizes and QoS guarantees can hold even when network links are operatedat 100% of their capacity, i.e., in practice links in the network can beoperated at close to 100% of its peak capacity. The bounds apply togeneral networks, including Internet Protocol (IP) and hierarchical IPnetworks, ATM networks, MPLS networks, IP networks using the IntegratedServices (IntServ) or Differentiated Services (DiffServ) service models,optical networks and wireless mesh networks. The routers can requireseveral orders of magnitude less buffers compared to current routerdesigns, i.e., buffer memory use in routers can potentially be reducedby factors of 100 to 10,000 or more. Routers will cost less to build,they will be smaller, they will have higher performance and higherenergy efficiency. Network links using these methods can operate atessentially 100% of their peak capacity, and there is no need forsignificant over-provisioning to achieve QoS guarantees. These methodscan make all-optical packet switched networks which operate at nearly100% of capacity with QoS guarantees viable, since the amount ofbuffering feasible in an all-optical router is limited to a very smallnumber of packets, for example 10-20 packet buffers per input port oroutput port.

Switches are important components of Internet Protocol (IP) routers,optical routers, wireless routers, ATM and MPLS switches, computingsystems and many other systems.

The textbook [3] by A. Leon-Garcia and I. Widjaja, entitled“Communication Networks, Fundamental Concepts and Key Architectures”,second Edition, McGraw Hill, 2004, describes several terms, includingInternet Protocol (IP) networks, MPLS networks, the Integrated Servicesand Differentiated Services models, the RSVP protocol, and ATM networks.The Internet carries variable-size Internet Protocol (IP) packets, whichtypically vary in size from 64 bytes up to a maximum of 1500 bytes.These packets are typically buffered in the switches and routers, andthe amount of buffers required in a typical router or switch can be verylarge. The buffers are typically organized into one of three basicqueuing schemes, the Input-Queued (IQ) Switches, the Output-Queued (OQ)switches, and the Crosspoint Queued (XQ) switches. Combinations of thesequeuing scheme are also used.

Input-Queued switches typically buffer packets at the input side of theswitch. The packets are scheduled for transmission through the switch tothe output side. The transmission from the input side to the output sidemay be accomplished using a slotted or unslotted switch. In a slottedswitch, a variable-size packet at the input size is first segmented intosmall fixed-sized packets called ‘cells’. The cells are scheduled andtransmitted through the switch to the output side, where the originalvariable-size packet may be reconstructed. A slotted switch operates indiscrete time-slots, where a time-slot has sufficient duration totransmit a cell from the input side to the output side. In contrast, inan unslotted switch the variable-size packet is transmitted through theswitch directly, without segmentation.

Our designs will apply to both slotted and unslotted switches.

An Output Queued switch places the buffers at the output side of theswitch. If multiple packets arrive simultaneously and if they all havethe same desired output port, then the switch must have an internal‘speedup’ to be able to deliver multiple packets to one output portsimultaneously. Speedup requires a higher memory bandwidth at the outputside of the switch than necessary, which increases the cost of theswitch and limits its practicality. Large OQ switches are consideredimpractical.

A Crosspoint Queued switch places the buffers or queues within theswitching matrix. There are typically N-squared crosspoints within theswitching matrix, and each crosspoint contains a queue with the capacityto store one or more packets. Crosspoint queued switches are easier toschedule than input queued switches, but they incur a cost of N-squaredbuffers within the switching matrix, which will increase the cost of theswitching matrix. It is well known that the cost of a silicon integratedcircuit is related to the VLSI area of the circuit, and the N-squaredbuffers will add a significant area requirement, which will increasecost.

Combinations of these basic buffering schemes are possible, for exampleCombined Input and Crosspoint Queued switches, and Combined Input andOutput Queued switches. The methods to be presented in this paper applyto all these switch designs.

A necessary condition to guarantee bounded queue sizes and near-perfectQoS for a selected traffic flow in a packet-switched network, regardlessof the mean rate of the traffic flow, is the concept of a bounded‘Normalized Service Lead/Lag’, here after denoted NSLL, which is definedin detail later in this document. Informally, the NSLL represents howmuch service a traffic flow has received, relative to the same flowreceiving perfectly scheduled service. A positive NSLL indicates thatthe flow has received more service than the perfectly-scheduled flow. Anegative NSLL indicates that the flow has received less service than theperfectly scheduled flow.

The proposed methods to achieve bounded router buffer sizes and strictQoS guarantees are a combination of techniques. First, eachapplication-layer traffic flow entering the network may be shaped at thesource node using an ‘Application-Specific Traffic Shaper’ or ASTSmodule. This ASTS module will accept bursty application-layer packets,and it will generate a stream of smooth network-layer packets which areinjected into the network with a bounded NSLL. Each provisioned trafficflow is assigned to one or more paths through the network, andsufficient bandwidth should be allocated (provisioned) for each flow oneach link in each path. Second, routers may use a switch-schedulingmethod which achieves a bounded NSLL for the traffic leaving the outputports of the switch. (Some routers may use switch scheduling methodswhich do not achieve a bounded NSLL, but some routers should re-shapethe traffic to achieve a bounded NSLL at least periodically.) Third, theswitch may use a flow-scheduling method to schedule each individualprovisioned traffic flow, to achieve a bounded NSLL for each provisionedtraffic flow departing the switch. (Some routers may use flow-schedulingmethods which do not achieve a bounded NSLL, but some routers shouldre-shape the traffic flows to achieve a bounded NSLL on each flow, atleast periodically.) Fourth, the bursty application-layer traffic flowsmay be reconstructed in ‘Application-Specific Playback Queue’ (ASPQ)modules at their destinations, to regenerate the original burstyapplication-layer traffic flows with strict QoS guarantees. Under thesecombination of conditions, it can be proven that a provisioned trafficflow can buffer as few as O(K) packets per router [18,19], where K is aninteger equal to the bound on the NSLL. (The bound of O(K) buffers perflow per router will be achieved if every router achieves the bounds onthe NSLL.) It can also be proven that every flow can achieve strictQuality of Service guarantees [18,19]. A bursty application-layertraffic flow can be regenerated at the destination node and can receivestrict QoS guarantees, where it can achieve a near-minimal normalizedend-to-end delay, a very low packet loss rate, and a very lownetwork-introduced delay jitter. (The normalized end-to-end delay of aflow is defined as the end-to-end delay of the flow, dividing by themean time between packets in a perfectly scheduled transmission for theflow.)

The proposed methods are in contrast to some methods currently in use inthe Internet. In the current Internet, most links and switches arescheduled so that any excess capacity on a link is exploited by trafficflows which have queued packets awaiting transmission. Consider the USpatent [4] by J. W. Marshal et al, entitled “Supplemental queue samplingtechnique for packet scheduling”, U.S. Pat. No. 7,640,355, December2009. This patent describes a technique in which the ‘excess capacity’of a link is allocated to traffic flows which have queued packets, toimprove the utilization of a link. Rather than having a link remainidle, these flows can receive extra service, to use up the excesscapacity of the link and improve the link's utilization. The difficultywith this approach is that it violates the property of the bounded NSLLof a traffic flow. A flow may receive more service than a perfectlyscheduled flow, for some period of time. Once this property of a boundedNSLL is violated for one flow, it may be violated for other flows, asthe flows do interfere with each other. The network can quicklydeteriorate to the case where all flows have lost the property of abounded NSLL. Therefore, one cannot bound the sizes of the routerbuffers in the Internet. Packets may be dropped at routers due to bufferoverflow. One cannot provide strict Quality of Service guarantees, andone cannot operate the network at 100% of its capacity, due to the largequeue sizes within the routers and the possibility of router bufferoverflow. To achieve the three desired goals of bounded router buffersizes, strict QoS guarantees and the ability to operate a network linkat nearly 100% of its capacity, the approach to utilize excess capacityon a link by offering extra service to traffic flows should not be usedexcessively, since it may increase the NSLL. Alternatively, if thisbandwidth-sharing approach is used extensively, some routers shouldperiodically re-shape traffic flows to achieve a bounded NSLL.

SUMMARY OF THE INVENTION

A method to achieve bounded router queue sizes and strict Quality ofService guarantees for provisioned application-layer traffic flows in apacket-switched network are described. In one embodiment, the networkcan be a packet-switched Internet Protocol (IP) network. In anotherembodiment, the IP network can use the Integrated Services orDifferentiated Services models. In another embodiment, the network canbe a packet-switched MPLS network. In another embodiment, the networkcan be an all-optical packet-switched network. In another embodiment,the network can be a packet-switched wireless mesh network. The switchesor routers in the network can use any combination of queueingdisciplines, for example Input Queueing, possibly in combination withcrosspoint queueing and/or output queueing. An ‘Application-SpecificTraffic Shaper’ module can be used to shape a potentially-burstyapplication-layer traffic flow at the traffic source node, to generate astream of network-layer packets. The network-layer packets associatedwith the application-layer traffic flow are injected into the networkwith a bounded normalized service lead/lag. One or more end-to-end pathsthrough the network may be provisioned for each traffic flow. Sufficientbandwidth should be allocated for the traffic flow on links in eachpath. An ‘Application-Specific Playback Queue’ module may be used ateach destination node, to regenerate the original potentially-burstyapplication-level traffic flows at every destination, with strictQuality of Service guarantees. A switch scheduling algorithm with abounded normalized service lead/lag may be used to schedule thetransmission of the provisioned traffic flows through some or allswitches or routers. Some or all switches or routers may use aflow-scheduling algorithm to schedule the transmission of theprovisioned traffic flows, so that the network-layer packets associatedwith each provisioned traffic flow will depart from the switch or routerwith a bounded normalized service lead. Under this combination ofconditions, it can be shown that a provisioned application-layer trafficflow can buffer O(K) packets per router, where K is the bound on thenormalized service lead/lag. By controlling the NSLL of traffic flows ortraffic classes, the amount of buffering required in an Internet routeror an MPLS switch can be reduced by several orders of magnitude, i.e.,potentially by factors of 100-10,000 or more, compared to current routertechnology. The method in which provisioned traffic flows are selectedfor service within a switch or router can have a significant impact onthe buffer sizes and the end-to-end performance. Three flow-schedulingmethods are defined and analysed. Work-conserving flow-schedulingmethods can guarantee a bounded normalized service lead/lag, whilenon-work-conserving flow-scheduling methods typically cannot make suchguarantees. To ensure a bounded normalized service lead/lag, theflow-scheduling method should not be work-conserving. To further reducebuffer requirements, aggregated traffic flows are considered. Eachaggregated end-to-end traffic flow can buffer O(K) packets per router,in addition to O(K) packet buffers per flow at the aggregation ordis-aggregation node. In another embodiment, the network can supportmultiple prioritized traffic classes, compatible with the IP IntegratedServices and Differentiated Services models. Each class of trafficrequires O(K) packet buffers per router.

Other aspects and features of the present invention will become apparentto those of ordinary skill in the art upon review of the followingdescription of specific embodiments of the invention in conjunction withthe accompanying figures.

BRIEF DESCRIPTION OF THE DRAWINGS

In the figures which illustrate by way of example only, embodiments ofthe present invention.

FIG. 1A shows an Input Queued IQ switch system.

FIG. 1B shows a Combined Input and Crosspoint Queued (CIXQ) switchsystem.

FIG. 1C shows a Combined Input-Input and Output Queued (CIIOQ) switchsystem.

FIG. 1D shows a CIXQ switch system in more detail.

FIG. 2A illustrates the cumulative arrival curve versus time for 2traffic flows with perfectly scheduled packet arrivals. FIG. 2Billustrates the cumulative arrival curve versus normalized time for 2traffic flows with perfectly scheduled arrivals.

FIG. 3A illustrates the cumulative arrival curve versus time for 2traffic flows with imperfectly scheduled packet arrivals. FIG. 3Billustrates the cumulative arrival curve versus normalized time for 2traffic flows with imperfectly scheduled arrivals.

FIG. 4A shows a Token Bucket Traffic Shaper. FIG. 4B shows a PlaybackQueue.

FIG. 5 shows an Internet network which can transmit a high-definitiondigital television traffic flow across the network withessentially-perfect Quality-of-Service guarantees.

FIG. 6A shows the distribution of video frame sizes in a high-definitiondigital video traffic flow. FIG. 6B shows the distribution of videoframe sizes in the digital video traffic flow, after the streams havebeen normalized to have the same mean value.

FIG. 7A shows an Input Port with Flow-VOQs for traffic flows withbounded buffer sizes and QoS guarantees. FIG. 7B shows anotherembodiment of an Input Port with Flow-VOQs for traffic flows withbounded buffer sizes and QoS guarantees.

FIGS. 8A and 8B show two methods Add_Flow and Remove_Flow.

FIG. 9A shows a method Static_Flow_Schedule, for computing aflow-transmission-schedule for a VOQ with bounded buffer sizes and QoSguarantees. FIG. 9B shows a method Find_Weight. FIG. 9C shows a slightlymodified method Static_Flow_Schedule RealTime, for computing aflow-transmission-schedule for a VOQ with bounded buffer sizes and QoSguarantees.

FIGS. 10A and 10B show two methods, Dynamic_Add_Packet, andDynamic_Remove_Packet, used in a method to dynamically schedule thetraffic flows in a VOQ with bounded buffer sizes and QoS guarantees.

FIGS. 11A and 11B show two methods Rand_Add_Packet and Rand_Rem_Packet,used in a method to randomly schedule the traffic flows in a VOQ.

FIGS. 12A, 12B, 12C, 12D, 12E and 12F illustrate the performance of themethod Static-Flow-Schedule from FIG. 9.

FIGS. 13A, 13B, 13C, 13D, 13E and 13F show performance of the methods todynamically schedule flows from FIG. 10.

FIGS. 14A, 14B, 14C, 14D, 14E and 14F illustrate the performance of themethods to randomly schedule flows from FIG. 11.

FIGS. 15A, 15B, 15C, 15D, 15E and 15F illustrate the performance of themethods to randomly schedule flows, when the traffic injected into thenetwork has a larger bound on the normalized service lead/lag, equal toplus or minus 20 packets.

FIGS. 16A, 16B, 16C, 16D and 16E show a traffic matrix, aVOQ-transmission-schedule, and a flow-transmission-schedule, for aninput queued switch.

FIGS. 17A and 17B shows routing tables for combining (aggregating)traffic flows.

FIG. 17C shows an Input Port which includes traffic shapers.

FIG. 17D shows an Input Port, which includes aggregation modules.

FIG. 18A shows an Input Port which supports traffic classes and trafficflows for QoS-enabled traffic, each with bounded buffer sizes and QoSguarantees.

FIG. 18B shows an Input Port which supports traffic classes and trafficflows for QoS-enabled traffic, with the addition of token bucket trafficshapers to regulate the NSLL of the traffic classes and traffic flows.

FIG. 19A illustrates an Input Port which supports QoS-enabled trafficwith QoS guarantees, which can co-exist with regular Best-EffortInternet traffic.

FIG. 19B illustrates the Input Port from FIG. 19A, in more detail.

DETAILED DESCRIPTION Basic Switch Designs

FIG. 1A illustrates a conventional Input queued (IQ) switch 10. IQSwitch 10 has N input ports 12 a, 12 b, . . . , 12 n on the left side,herein collectively and individually referred to as input ports 12. IQSwitch 10 has N output ports 14 a, 14 b, . . . , 14 n on the bottom,herein collectively and individually referred to as output ports 14. Ingeneral the switch may have N input ports and M output ports. Each inputport 12 has a router module 20, a VOQ demultiplexer switch 15, N VirtualOutput Queues (VOQs) 16, and a VOQ multiplexer switch 18. TheVOQ-demultiplexer switch 15 is also called a VOQ-demultiplexer 15. TheVOQ multiplexer switch 18 is also called a VOQ-server 18.

The switch 10 can use variable-size or fixed-sized packets. Eachincoming packet of data contains destination information in its header.The routing module 20 processes each incoming packet, to determine theappropriate output port 14 of the switch 10. In an Internet Protocol(IP) network, the routing module 20 may process IP packet headers, forexample IPv4 or IPv6 packet headers, to determine the output port. An IPnetwork can use several service models, such as the integrated Servicesand Differentiated Services models. In these models, the routing module20 may examine IP packet headers to identify packets which are handledby these models, and to determine the output port. In an MPLS network,the routing module 20 may process the MPLS packet headers to identifythe desired output port 14 of the switch 10. The Routing Module 20controls the VOQ-demultiplexer 15 through a control signal (not shown),to forward the incoming packet into the appropriate VOQ 16 associatedwith the desired output port 14. The routing module 20 may also performtraffic policing functions. Traffic policing functions are described in[3].

Let the N VOQs 16 at each input port 12 j be denoted VOQ 16(j,k), forinput ports 1<=j<=N and output ports 1<=k<=N, herein collectively andindividually referred to as VOQs 16. Each VOQ 16(j,k) stores all thepackets at input port 12 j which are destined for output port 14 k.Switch 10 also includes an N×N ‘switching matrix 22. The switchingmatrix 22 contains N-squared crosspoints 28, at the intersection of eachrow 24 and column 26. A programmable ON-OFF crosspoint switch exists ateach crosspoint (not shown in FIG. 1A), to connect a row 24 to a column26. When the crosspoint switch (j,k) is enabled, a cell which istransmitted by input port 12 j on a row 24 j will appear at on column 24k and output port 14 k. The switching matrix 22 is typically implementedon one or more VLSI integrated circuits which typically reside on one ormore printed circuit boards, which in turn reside in a rack or cabinetof electronic equipment (not shown in FIG. 1A). Links 31 connect theinput ports 12 to the switching matrix 22.

FIG. 1B illustrates a simplified model of a combined input andcrosspoint queued (CIXQ) switch 30. CIXQ switch 30 has N input ports 12and N output ports 14, and a switching matrix 32. Each input port 12 hasa routing module 20, a VOQ-demultiplexer switch 15, up to N VirtualOutput Queues (VOQs) 16, and a VOQ-multiplexer switch 18, also called aVOQ-server 18. Each crosspoint 28 in the switching matrix 32 has anassociated crosspoint queue 34, denoted as XQ 34, capable of storing oneor more packets or cells of data. During an interval of time, an inputport 12 j can transmit one packet of data from one VOQ 16(j,k), over thetransmission line 31 j to the switching matrix 32. The packet will bedirected into the appropriate XQ 34 in row 24 j by logic (not shown inFIG. 1B). Similarly, during an interval of time, each column 26 k of theswitching matrix can transmit one packet of data from one non-empty XQ34 in column 26 k, over the outgoing transmission line 27 k to theoutput port 14 k.

FIG. 10 illustrates a switch using combined input and output queueing,denoted the CIIOX switch since it has 2 levels of input queues, each ofwhich must be scheduled. The input ports 12 have the same structure asshown in FIG. 1A. The switching matrix 32 consists of internal inputqueues 35 and internal output queues 36. Each input port 12 has anassociated internal input queue 35 within the switching matrix 32.Packets are sent from the input ports 12 to the internal input queues35. Therefore, there are two levels of input queues, and transmissionsfrom each level of input queue should be scheduled. Each output port 14has an associated internal output queue 36 within the switching matrix32. Each internal input queue 34 has an input-demultiplexer 38. Eachinternal output queue has an associated output multiplexer 40. The inputdemultiplexers 38 and the output multiplexers 40 must be scheduled tomove packets from the internal input queues 34 to the internal outputqueues 36. Limited speedup can be introduced to the switching matrix 32to simplify this scheduling if desired. For example, the internal inputqueues 34 may be able to remove 2 packets simultaneously per time-slot,or the internal output queues 36 may be able to receive up to 2 packetssimultaneously per time-slot.

FIG. 1D illustrates a more detailed view of a CIXQ switch shown in FIG.1B. The input ports 12 have the same structure as shown in FIG. 1A,where each input port 12 is associated with one row 24 of the switchingmatrix. The switching matrix 32 consists of N rows 24. A packettransmitted from an input port 12 j and is delivered to the desired XQ34 in the same row using information in the packet header. The packetcan be delivered to an XQ in a row using a row bus, or by using ademultiplexer with horizontal wires, as shown in FIG. 10. Each outputport is associated with one column of the switching matrix. Each outputport has an associated output multiplexer 37, which is used to select apacket from an XQ 34 in the same column, and forward it to the outputport.

Traffic Arrival Curves and Service Lead/Lag

FIG. 2A illustrates the concept of the Cumulative Arrival Curve on agraph. Assume that the packets are fixed-sized, i.e., a fixed-sizepacket can be called a cell and each cell may have 64, 256 or 1,024bytes. The y-axis denotes the number of an arriving packet. The x-axisdenotes the arrival time, which is measured in milliseconds. Thearriving packets for two perfectly-scheduled traffic flows are shown bythe dots 62 and 66. The rate of flow #1 is fixed at 1 packet every 10milliseconds. Points 62 denote the arrival times of the packets in flow#1. For example, point 62 a denotes the 1st packet in flow #1, point 62b denotes the 2nd packet in flow #1, etc. The arriving packets in flow#1 are perfectly spaced apart in time. Each packet j arrives at itsperfect arrival time of j*10 milliseconds, for j>=1.

The time between 2 consecutive arrivals is called the Inter-Arrival-Time(IAT), as denoted by the arrow 68. The time between 2 consecutivearrivals in a perfectly scheduled traffic flow is call the ‘IdealInter-Arrival-Time’ (IIAT). The time between 2 consecutive departures iscalled the Inter-Departure-Time (IDT). The time between 2 consecutivedepartures in a perfectly scheduled traffic flow is call the ‘IdealInter-Departure-Time’ (IIDT). The points 62 for arriving packets in flow#1 can be joined by a straight line 60 in FIG. 2A. This line 60 denotesthe Ideal Cumulative Arrival Curve for traffic flow #1. Its slope isequal to the rate of the traffic flow, i.e., 1 packet every 10milliseconds. Given any perfectly-scheduled traffic flow, when itspacket arrivals are plotted on FIG. 2A, the arrivals will lie on astraight line with a slope determined by the rate of the flow.

The rate of flow #2 is fixed at 1 packet every 5 milliseconds. Thearriving packets in flow #2 are also perfectly scheduled, i.e.,perfectly spaced apart in time. Points 66 denote the arrival times ofthe packets in flow #2. Each packet j arrives at its perfect arrivaltime of j*5 milliseconds. The points 66 for arriving packets in flow #2can also be joined by a straight line 64 in FIG. 2A. This line 64denotes the Ideal Cumulative Arrival Curve for traffic flow #2. Itsslope is equal to the rate of the traffic flow, i.e., 1 packet every 5milliseconds.

Many mathematical proofs for establishing bounds on the sizes of packetqueues use graphical arguments. These graphical methods typically plotthe Cumulative Arrival Curve and Cumulative Departure Curve for a queueon one graph, and then infer the maximum queue size. The textbook [26]by D. Bertsekas and R. Gallager, entitled ‘Data Networks”, 2nd edition,Prentice Hall, 1992 describes graphical techniques to analyse queues andestablish Little's theorem, on pages 152-157.

It is difficult to plot the cumulative arrival curves of multiple flowson one graph, when all the traffic flows have different rates. If we areprocessing for example 1000 traffic flows, all with different rates,there will be 1000 different Cumulative Arrival Curves on one graph, allwith different slopes. Therefore, it is difficult to create one theoremwhich applies to thousands of distinct traffic flows, each with adifferent rate. To overcome this problem, we propose to change thex-axis in the graph to a normalized time.

FIG. 2B illustrates the concept of the Normalized Cumulative ArrivalCurve on a graph. Assume that the packets are fixed-sized (i.e., cells).The y-axis denotes the number of an arriving packet. The x-axis of thegraph denotes the normalized arrival time. The normalized arrival timeof a packet is equal to its arrival time, divided by theIdeal-Inter-Arrival-Time (IIDT) for the traffic flow. In FIG. 2B thearriving packets in flow #1 are perfectly scheduled in time. In thesteady-state a traffic flow at a queue has the same arriving rate anddeparting rate. Therefore, the Ideal IAT equals the Ideal IDT, i.e.,IIAT=IIDT. In Flow #1, each packet j arrives at its perfect arrival timeof j*10 milliseconds, equivalently each packet j arrives at normalizedtime equal to j IIDT. Therefore, packet 1 arrives at time 1 IIDT asshown by point 62 a, packet 2 arrives at time 2 IIDT as shown by point62 b, etc. Observe that the points 62 for arriving packets in flow #1can be joined by a straight line 70 in FIG. 2B. This line 70 denotes theNormalized Ideal Cumulative Arrival Curve for traffic flow #1. Its slopeis equal to the rate of the traffic flow, i.e., 1 packet every IIDT.

In FIG. 2B the arriving packets in flow #2 are also perfectly scheduledin time. Each packet j arrives at its perfect arrival time of j*5milliseconds, equivalently each packet j arrives at a normalized timeequal to j IIDT. Therefore, packet 1 arrives at time 1 IIDT as shown bypoint 66 a, packet 2 arrives at time 2 IIDT as shown by point 66 b, etc.The points 66 for arriving packets in flow #2 can also be joined by astraight line 70 in FIG. 2B. This line 70 also denotes the NormalizedIdeal Cumulative Arrival Curve for traffic flow #2. Its slope is equalto the rate of the traffic flow, i.e., 1 packet every IIDT.

Observe that one graph can now represent thousands of traffic flows,each with a different traffic rate, in FIG. 2B. Every traffic flow hasone Normalized Ideal Cumulative Arrival Curve, with a slope of 45degrees, i.e., 1 cell arrives every IIAT. Every traffic flow has oneNormalized Ideal Cumulative Departure Curve, with a slope of 45 degrees,i.e., 1 cell departs every IIDT.

FIG. 3 illustrates the arrivals of 2 traffic flows, which are notperfectly scheduled. Points 74 correspond to the arrival times of cellsin a traffic flow #3 which exhibits a normalized service lag. Inparticular, the first cell denoted by point 74 a arrives late atnormalized time 3 IIDT, so this traffic flow experiences a normalizedservice lag. The normalized service lag is 2 packets, since the flow hasreceived 2 fewer packets than a perfectly scheduled for flow. Inparticular, packets were not received at times 1 IIDT and 2 IIDT. Points75 correspond to the arrival times of cells in traffic flow #4 whichexhibits a normalized service lead. The normalized service lead is 2packets, since the flow has received 2 more packets than a perfectlyscheduled flow. In particular, 2 extra packets were received at time 0IIDT.

FIG. 3B illustrates the occupancy of a queue, given a normalizedarriving packet stream and a normalized departing packet stream. Thecumulative arrival curve has an upper bound at any normalized time,which is illustrated by line segments 78 a, 78 b, 78 c. These linesegments indicate that this traffic flow has a normalized service leadof at most 2 cells. The cumulative departure curve has a lower bound atany normalized time, which is illustrated by line segments 79 a, 79 b,79 c. These line segments indicate that this traffic flow has anormalized service lag of at most 2 cells. At any given normalized time,the vertical difference between the cumulative arrival curve 78 andcumulative departure curve 79 equals the number of packets in the queue.For example, the vertical line 81 illustrates that a queue thatexperiences this cumulative arrival curve and cumulative departure curvewill have at most 4 packets. If the cumulative arrival curve has abounded NSLL of K cells, where K is a small integer, and the cumulativedeparture curve has a has a bounded NSLL of K cells, then the maximumnumber of packets in the queue is bounded by 2K in this example.

It is shown in [19] that provided the cumulative arrival stream has abounded NSLL<=K packets and the cumulative departure stream has abounded NSLL<=K packets, then the number of packets in any queue isbounded by a small integer multiple of K. For the case of variable-sizepackets, the same curves and methodology apply. However, the y-axis canbe expressed in terms of bytes of data served, rather than packetsserved, and the x-axis can be expressed in the IIDT for a single byte.

Formal Definitions and Theorem

Assume a network of slotted switches, where fixed-sized packets aretransmitted through the network. A time-slot has sufficient time toallow a packet to be transmitted from an input port to an output port ina switch or router.

Definition: A traffic flow f consists of a series of packets transmittedfrom one source node to one destination node, in a network. A sourcenode may be identified by an IP address and a port number. A destinationnode may be identified by an IP address and a port number.

Definition: A traffic flow f can be provisioned in a network by ensuringthat sufficient bandwidth exists on the edges in the network that theflow traverses.

The following definitions apply to a selected queue in a network.

Definition: Let s(f,c) denote the service time of packet c in flow f.The ‘Inter-Departure Time’ (IDT) of packet c in a provisioned flow f isdefined as s(f,c)-s(f,c−1) for c>=2. The ‘Ideal Inter-Departure Time’(IIDT) of packets in a provisioned flow f with a guaranteed traffic rateequal to rate(f) time-slot reservations per frame is given byIIDT(f)=F/rate(f) time-slots.

Definition: The ‘Service lead/lag’ of a traffic flow f at time-slot t isdefined as the cumulative service (expressed in bytes) received bytraffic flow f at time-slot t, relative to the cumulative servicereceived by a perfectly-scheduled flow with the same rate at time-slott. Intuitively, a positive Service Lead/Lag represents how many bytesbehind service the flow has fallen, relative to an ideal serviceschedule. A negative Service Lag is called a Service Lead, andrepresents how many bytes ahead of service the flow has moved, relativeto an ideal service schedule. (The NSLL is different from the network‘jitter’, since the jitter does not compare the cumulative receivedservice to the cumulative ideal service.)

Definition: The ‘Normalized Service Lead/Lag’ (NSLL) of a flow f at timet is defined as the Service Lead/Lag of the flow f at normalized timet*IIDT, expressed as fractions of a fixed packet size, where IIDTdenotes the Ideal Inter-Departure Time of the fixed-sized packets in theflow. A positive NSLL represents how many packets behind schedule theflow has fallen, relative to an ideal service schedule. A negative NSLLrepresents how many packets ahead of schedule the flow has moved,relative to an ideal service schedule. (The NSLL can also be defined forvariable-sized packets, for example by treating one byte as thefixed-packet size in the prior definition.)

The following four theorems have been established in the paper [19] byT. H. Szymanski entitled “Bounds on End-to-End Delay and Jitter inInput-Buffered and Internally-Buffered IP Networks”, presented at theIEEE Sarnoff Symposium, Princeton, N.J., March 30-Apr. 1, 2009, whichwas incorporated by reference earlier. These theorems assume that everytraffic flow is shaped at the entry point to the network to have abounded NSLL. These theorems assume that every switch or routerschedules its traffic flows so that every provisioned traffic flowdeparting a switch or router has a bounded NSLL. They also assume thatpackets have a fixed size, for example 1 Kbytes on a backbone network,and that the scheduling frame has a fixed duration. However, the similartheorems and bounds apply for variable-size packets operating inunslotted networks.

Theorem 1:

Given a flow f traversing a queue, with a normalized cumulative arrivalcurve which has a bounded normalized service lead/lag of <=K packets,and with a normalized cumulative departure curve which has a boundednormalized service lead/lag of <=K packets, then the maximum queue sizeis a small multiple of K packets, typically 4K packets.

Theorem 2:

When all queues in all intermediate routers have reached steady-state,the maximum end-to-end queueing delay of a provisioned guaranteed-rateflow traversing H routers is O(KH) IIDT time-slots.

Theorem 3:

In the steady-state, the departures of traffic flow fat any router alongan end-to-end path of H routers are constrained by the schedulingopportunities, and will exhibit a maximum normalized service lead/lag ofK packets. In other words, the normalized service lead/lag of a flow isnot cumulative when traversing multiple routers.

Theorem 3:

In the steady-state, if an arriving traffic flow has a bounded NSLL, andthe switch or router uses a scheduling algorithm with a bounded NSLL,then every provisioned traffic flow which departs the switch or routerhas a bounded NSLL. In other words, the normalized service lead/lag of aprovisioned flow is not cumulative when traversing multiple switches orrouters.

Theorem 4:

A provisioned traffic flow which traverses H switches or routers alongan end-to-end path can be delivered to the end-user with zeronetwork-introduced delay jitter, when an appropriately sizedApplication-Specific Playback Queue module is employed.

Theorem 1 states that the number of packets buffered for any provisionedflow in any router in any network can be limited to a small integermultiple of the NSLL bound of K for all loads up to 100%. Theorem 2states that provisioned end-to-end traffic flows may experience nocongestion, excessive delay or throughput degradation. A provisionedend-to-end flow can experience a small but effectively negligiblequeueing delay at a router compared to current router technologies.Theorem 3 states that the normalized service lead/lag is not cumulativewhen traversing multiple routers in any network. This property allowsnetworks to grow to arbitrary sizes, where traffic flows can passthrough hundreds of routers and the performance will not degrade,provided that the traffic is periodically re-shaped to have a boundedNSLL. Theorem 4 states that every provisioned end-to-end traffic flowcan be delivered at every destination router with strict end-to-endQuality of Service guarantees. In particular, a bursty application-layerhigh-definition IPTV traffic flow can be transmitted through a networkand can be regenerated at every destination router with strict QoSguarantees, with small normalized queueing delays, with small packetloss rate and small delay jitter. The service each flow receives will be‘essentially-perfect’ if every router along an end-to-end path achievesa bounded NSLL. The service each flow receives will be very good ifoccasional routers along an end-to-end re-shape traffic to achieve abounded NSLL. The simulation results reported in FIGS. 12, 13 and 14will demonstrate these 4 theorems.

These theorems are very general, and apply to any type of switch,including the input queued switch in FIG. 1A, the CIXQ switch in FIG.1B, and the CIIOQ switch in FIG. 10. They also apply to any type ofpacket switched network, i.e., an Internet Protocol network, an MPLSnetwork, an optical network or a wireless network.

Traffic Shaping

FIG. 4A illustrates a Token Bucket Traffic Shaper module 82. The trafficshaper module accepts in incoming bursty application-layer traffic flow,corresponding to some multimedia application, for example a compressedhigh-definition video stream. The application-layer traffic flowconsists of application-layer packets, which may have very largedifferences in sizes. Application-layer video packets may vary in sizefrom 1,000 bytes up to 500,000 bytes, and they may arrive at regulartime intervals, such as 30 packets per second, creating an extremelybursty traffic flow. The token bucker traffic shaper module 82 can bedesigned to smoothen out the bursts in the application-layer trafficflow. The large variable-size application-layer packets may be convertedto smaller relatively fixed-sized network-layer packets, for example1000 bytes each. (The network layer packets need not be strictly fixedsize, they may have some variability.) The network-layer packets can bequeued, processed and may then be injected into the network with asufficiently small normalized service lead/lag. The token bucket shapermodule 82 will accept a bursty application-layer traffic flow, and maygenerate a stream of network-layer packets with a low normalized servicelead/lag, for injection into the network.

Referring to FIG. 4A, the shaper module 82 includes a PacketSegmentation unit 87, a Data-Queue 83, a Token Queue 84, aToken-Controlled-Server 85, and a Token Generator 86. Incomingapplication-layer packets arrive into the segmentation unit 87. Theapplication-layer packet may represent a high-definition digital videoimage, or some other multimedia information. The segmentation unit 87may segment a large application-layer packet into several smaller sizednetwork-layer packets, for example network-layer packets with a maximumsize of 1 Kbytes each. These network-layer packets are forwarded to thedata queue 83. Network-layer packets will hereafter be referred to aspackets. The token generator 86 generates tokens periodically, which arestored in the token queue 84. Each token represents permission for theserver 85 to remove a predetermined amount of data from the data queue83. A token may represent permission to send for example 64 bytes, or256 bytes, or 1 Kbytes of data. The token-controlled server 85 willremove the head-of-line packet from the data queue 83 and transmit it,when some or all of the tokens in the token queue 84 together havesufficient permission to send the packet. Once the packet is sent, thetokens whose permissions was used are removed from the token queue 84.The token bucket shaper 82 can work with fixed-sized packets (cells) orwith variable-size packets. A token bucket traffic shaper 82 isdescribed on pages 554-558 in the textbook [3].

FIG. 4B illustrates a Playback Queue module 88. The playback queuemodule 88 operates in tandem with a corresponding token bucker trafficshaper module 82. The playback queue 88 is used to accept an incomingstream of maximum-sized network-layer packets generated by a tokenbucket traffic shaper module 82 corresponding to a burstyapplication-layer traffic flow, and to regenerate the burstyapplication-layer traffic flow on the output stream. The incomingnetwork-layer packets will typically arrive at the playback queue module88 with a bounded normalized service lead/lag, so that the time taken toreconstruct every variable-size application-layer packet can be computedand it is upper-bounded. The application-layer packets on the outputstream are generated and released, so that the output stream isessentially an exact model of the incoming bursty application-layertraffic flow received at the corresponding traffic shaper module 82,except delayed in time.

The playback queue module 88 consists of a controller 89, a packet queue90, a reassembly queue 91 and a playback server 92. The controller 89will process the incoming stream of packets. The controller 89 willcontrol the reassembly unit 91 to reassemble the application-layerpacket, and the controller 89 will control the playback server 92 torelease the application-layer packet at the appropriate time.

FIG. 6 is described next, followed by FIG. 5. FIG. 6 illustrates thecharacteristics of a bursty high-definition application-layer videotraffic flow. The application-layer video traffic flow has 30 videoframes per second, where each video frame consists of the compresseddata for a digital image. These video frames are called theapplication-layer packets. The x-axis in FIG. 6A indicates the number ofKilobytes in an application-layer packet. The y-axis illustrates theprobability of occurrence. For a single video traffic flow, the averageapplication-layer packet has a size of 13.56 Kbytes, while the maximumapplication-layer packet has a size of 319 Kbytes.

FIG. 6 also illustrates the results for an aggregation of 10high-definition video traffic flows.

In this aggregated traffic flow, 10 application-layer packets from 10video streams arrive simultaneously, 30 times per second. These 10application-layer packets are viewed as belonging to one largerapplication-layer packet belonging to the aggregated application-layervideo traffic flow. The burstiness of the aggregated video traffic flowis reduced. Referring to FIG. 6B, the single video traffic flow has ahigh burstiness, where the largest application-layer packet may be wellover 10 times larger than the average size of an application-layerpacket. Referring to FIG. 6B, the aggregated video traffic flow has alower burstiness, where the largest aggregated application-layer packetmay be only about 4 or 5 times larger than the average size of theaggregated application-layer packet. The more application-layer flowsthat are aggregated, the less bursty the resulting aggregated trafficflow is. The token bucket shaper module 82 and the playback queue module88 can be designed to regenerate aggregated traffic flows too, inaddition to individual traffic flows. In general, the higher the levelof aggregation, the lower the burstiness of the aggregated traffic flow.Define the normalized buffer size as the maximum size of a bufferdivided by the average size of the buffer. Traffic flows with higherlevels of aggregation will have lower burstiness, and will result insmaller normalized buffer sizes in the traffic shaper module 88 and theplayback module 88, to regenerated the output streams.

FIG. 5 illustrates a network, consisting of routers (or switches) 95 andlinks (or edges) 98 between routers. The routers 95 can use the routeror switch designs in FIG. 1A, 1B, 1C or 1D. Consider the transmission ofa digital video stream from source node 93 to destination node 99through the network as shown in FIG. 5. Variable-size application-layervideo packets may be processed by a Token Bucket Traffic Shaper module82 located at source node 93. This token bucket traffic shaper module 82is designed explicitly for the application-layer traffic flow ofhigh-definition digital video, as shown in FIG. 6. Therefore, this tokenbucket traffic shaper module 82 is called an ‘Application-SpecificTraffic Shaper’ module 82. In this video application, the traffic shapermodule 82 accepts application-layer packets 30 times a second, with anaverage size of 13.56 Kbytes, and a maximum size of 319 Kbytes. Itsegments these application-layer packets into network-layer packets,which are injected into the network. The network-layer packets can havefixed or variable size. Let the network layer packets have a maximumsize of 1 Kbytes. The network-layer packets are injected into thenetwork, with a bounded NSLL. For example, if the token bucket has adepth of K packet tokens, then the NSLL has a bound of approx. Kpackets, and network-layer packets are injected into the network withinK IIDT of their ideal injection time in a perfectly scheduled trafficflow.

Multiple traffic flows from the same or different applications maycompete with each other at a source node 93, for injection into thenetwork. In this case, the GPS/WFQ scheduling method can be used toselect packets to inject from multiple competing flows, such that theNSLL of every flow is bounded to a sufficiently small number. Forexample, the methods of FIGS. 9 and 10 to be described ahead can be usedat the source node.

In FIG. 5, an application-layer traffic flow may be provisioned from thesource node 93 to the destination node 99, using a protocol similar tothe Internet Resource Reservation Protocol (RSVP) which is described inthe textbook [3]. A provisioned traffic flow may be routed over 1end-to-end path from the source node to the destination node, or it mayuse multiple end-to-end paths from the source node 93 to the destinationnode 99. For example, one path 96 may use links 96 a, 96 b and 96 c.Another path 97 may use links 97 a, 97 b, and 97 c. The provisioningprotocol may allocate a fixed amount of bandwidth for the traffic flow,for links along each end-to-end path. Each end-to-end path associatedwith a provisioned traffic flow should support a fixed amount ofbandwidth for the traffic flow, and the fixed bandwidths for eachend-to-end path can be different. Therefore, each end-to-end pathcarrying traffic for a provisioned traffic flow may have its owndata-rate and IIDT. Source node 93 can transmit network-layer packetswith a small and bounded normalized service lead/lag, along eachprovisioned end-to-end path. The traffic shaper 82 at source node 93will constrain the transmission of packets to have an average rate, amaximum rate and a maximum NSLL, for each end-to-end path. Source node93 will incur a queuing delay, since the bursty application-layerpackets are segmented may be queued before they are transmitted with abounded NSLL. There may be many network-layer packets stored in the dataqueue 83 of the token bucket traffic shaper module 82 at source node 93at any one time.

If multiple end-to-end paths are used to support one provisioned trafficflow, then the token bucket traffic shaper 82 in FIG. 4A can bemodified. In one embodiment, each path can have its own traffic shaper82 configured at an appropriate traffic rate (i.e. the rate assigned tothe path). In another embodiment, there is one shared data queue 83. Theunits 85, 84 and 86 are replicated for each end-to-end path, and areconfigured at an appropriate traffic rate (i.e. the rate assigned to thepath). In both embodiments, the end-to-end delay along the paths can besmall and bounded, which makes the reconstruction of theapplication-layer packets at the destination node relatively easy.

In FIG. 5, the network-layer packets are transmitted over theprovisioned end-to-end path(s), for example the path 96 denoted by lines96 a, 96 b, 96 c, to the destination node 99. Hereafter, the phrase‘packet’ denotes a network-layer packet. The destination node 99 has aplayback queue module 88. The playback queue module 88 will receivenetwork-layer packets belonging to one application-layer traffic flow,and reconstruct the original bursty application-layer packets which weresegmented and transmitted at the source node 93. The playback queuemodule 88 may have to re-order packets slightly, if packets are receivedover multiple end-to-end paths. Destination node 99 will also incur aqueuing delay, since fixed-size network-layer packets may be receivedwith a bounded NSLL, they must be queued in the playback queue 90, andthe original bursty application-layer packets should be reassembled andreleased by the playback server 92 at the rate of 30 video frames persecond.

The bandwidth provisioned for one traffic flow along links 96 in one ormore end-to-end paths should have sufficient capacity to transmit theapplication-layer video stream. The average bit-rate of the video streamin FIG. 6 is 4.85 million bits per second, or roughly 592 Kbytes persecond. To transmit this traffic flow through the network, bandwidthshould be provisioned over one or more end-to-end paths at a rate notless than this amount. The queueing delay at the source node 93 and thedestination node 99 is closely related to the total amount of bandwidthprovisioned for the traffic flow. For a small queuing delay, the totalamount of provisioned bandwidth should have some ‘excess capacity’,i.e., the provisioned rate should be greater than 592 Kbytes per second.The ‘excess capacity’ will determine the queueing delays at the sourcenode 93 and the destination node 99. For low levels of aggregation, anexcess capacity of 10-50% percent will typically result in queuingdelays in the range of a few seconds, while an excess capacity in therange of 50-100% or more will typically result in queueing delays in therange of fractions of a second. For high levels of aggregation, anexcess capacity of only 1-5% percent can typically result in queuingdelays in the range of fractions of a second.

Flow Scheduling Algorithms

To achieve bounded queue sizes in a router 95 in FIG. 5, a traffic flowdeparting a switch or router 95 in FIG. 5 should achieve a boundedNSLL<=K, as stated in theorem 1.

The routers 95 in FIG. 5 may use the router designs in FIG. 1A, FIG. 1B,or FIG. 1C. Referring to FIG. 1A, it is possible that thousands oftraffic flows share one VOQ in a national backbone router. In FIG. 1A,in each input port 12, each VOQ 16 is served by a VOQ-server 18.Whenever a VOQ 16 is selected for service in a time-slot, there may bepotentially thousands of traffic flows associated with the VOQ 16 whichare candidates for service. Methods to schedule traffic flows within aVOQ which guarantee that each traffic flow achieves a bounded NSLL arerequired.

The IQ switch 10 in FIG. 1A has two important constraints that must besatisfied when scheduling packets between input ports 12 and outputports 14. Constraint #1 requires that in each time-slot, every inputport 12 transmits at most one packet to at most one output port 14.Constraint #2 requires that in each time-slot, every output port 14receives at most one packet from at most one input port 12. Effectively,in each time-slot each input port 12 is connected to at most 1 outputport 14, and each output port 14 is connected to at most one input port12. The paper [18] describes a method which can be used to schedule anIQ switch. A switch with N input ports and N output ports requires anN×N traffic rate matrix T. The matrix T can be maintained by anautonomic network controller according to current or anticipated trafficdemands, or it can be maintained by a network administrator according tocurrent or anticipated traffic demands. Each element T(i,j) specifiesthe requested number of transmission opportunities (time-slots) betweeninput port 12 i and output port 14 j, in a scheduling frame consistingof F time-slots. The method in [18] can be used to process the trafficmatrix T, and compute a ‘VOQ-transmission-schedule’ for each input port12 i of the IQ switch 10. A VOQ-transmission-schedule is a vector ‘VOQS’of length F. Each element VOQS(t) controls the input port 12 i for onetime-slot t, where 0<=t<F. If VOQS(t)=−1, then the input port 12 i isnot enabled to transmit any packet from any VOQ during that time-slot.If VOQS(t)=an integer j for 0<=j<N, then the input port 12 i is enabledto transmit one packet from the chosen VOQ(i,j) to output port 14 j inthe time-slot. The method in [18] can used to schedule the transmissionsfrom VOQs in the switch in FIG. 1A. The method in [18] will guaranteethat the total traffic leaving each VOQ has a bounded NSLL. However, themethod in [18] provides no guarantees on the NSLL for the individualtraffic flows which are associated with each VOQ.

Input Port Design for Static Flow-Scheduling Methods

FIG. 7A illustrates an input port 12 from FIG. 1A in more detail. Thisinput port 12 can use the method Static-Flow-Schedule shown in FIG. 9A,to guarantee that every traffic flow within a VOQ 16 will receive abounded NSLL. The input port 12 consists of the routing module 20, theVOQ-demultiplexer 15, the VOQs 16, and the VOQ-server 18, which wereshown in FIG. 1A. Each VOQ 16 has an associated VOQ-module 100. EachVOQ-module 100 consists of a flow-controller 102, a flow-demultiplexer104, a set of flow-VOQs 106, a flow-server 108, and an optionalcontroller 105, which may contain a look-up-table to store controlsignals for the flow-server 108. Each traffic flow f passing through aVOQ 16 is assigned its own flow-VOQ 106, which contains the packetswhich belong to the flow f. The flow-VOQ 106 is not necessarily aseparate memory or separate structure from the VOQ 16. The flow-VOQs 106could be ‘virtual’ and exist as logical abstractions. For example, theVOQ 16 can be implemented in one block of memory, and all the flow-VOQs106 associated with the VOQ can be implemented using pointers to thesame memory. Each input port 12 also has an input-port-controller 110,also called an IP-controller 110.

FIG. 7B illustrates an input port 12, where the VOQ-modules 100 havereplaced the VOQs 16. Therefore, when a packet is forwarded to a VOQ 16,it is forwarded and stored in the VOQ-module 100, as the VOQ has beenreplaced by the VOQ-module. FIG. 7B illustrates the concept that theVOQ-modules 100 and the VOQs 16 can represent the same physical memory.

Referring to FIG. 7A, packets arriving to the input port 12 areprocessed by the routing module 20. The routing module 20 processes thepacket header and determines the appropriate output port 14 and theappropriate VOQ 16 to store the packet. The routing module 20 controlsthe VOQ-demultiplexer 15 to forward the packet towards the appropriateVOQ-module 100. Within the VOQ module 100, the packet is first forwardedto the flow-controller module 102, which processes the packet header anddetermines which flow the packet belongs to. The flow-controller 102forwards the packet to the appropriate flow-VOQ 106, and updates itsinternal state. The flow-controller 102 maintains the number of packetsin each flow-VOQ 106 in its internal state.

The flow controller 102 may also implement a traffic policing algorithm.A typical traffic policing algorithm is described in [3] on pages550-558. A traffic policing algorithm may process incoming packetsassociated with a traffic flow, to ensure that those packets conform toa traffic profile associated with the traffic flow. A traffic profilemay specify an average data rate, a burst data rate, and a maximum burstsize. If some packets in a traffic flow do not conform to the trafficprofile, they may be marked as nonconforming, and they may be dropped.Dropped packets will not be forwarded into a flow-VOQ 106.

Scheduling in an Input Queued switch shown in FIG. 1A is known to be adifficult problem. The method in [18] by T. H. Szymanski can be used toschedule the IQ switch in FIG. 1A. Referring to FIG. 1A, given a trafficrate matrix which specifies the requested traffic rates between theinput ports 12 and output ports 14, this algorithm will compute theVOQ-transmission-schedules used by the IP controllers 110, which willcontrol the VOQ-servers 18. The algorithm in [18] will scheduletransmissions between the input ports 12 and the output ports 14 in anIQ switch, for a scheduling frame consisting of F time-slots. It willguarantee that the total traffic leaving any VOQ 16 in any input port 12will have a bounded NSLL. However, it will not guarantee that everytraffic flow leaving a VOQ 16 will have a bounded NSLL. Referring to aninput port 12 shown FIG. 7A, the VOQ-server 18 will be activated by theIP-controller 110 in certain time-slots when the input port 12 isenabled to transmit a packet to an output port 14 from the appropriateVOQ 16. The IP-controller 110 will enable the VOQ-server 18 to transmita packet from the given VOQ 16. The flow-controller 102 will control theflow-server 108 associated with the VOQ 16, to select an appropriateflow-VOQ 106 to service, when the associated VOQ 16 has been selectedfor service.

In the paper [18], it was also proven that any recursive schedulingalgorithm which schedules the packets in a traffic flow relativelyevenly over each half of a time interval, such that the amount oftraffic allocated to each half of the time interval differs by aconstant number of packets, will achieve a bounded NSLL for the trafficflow, provided that the length of the time-interval is bounded. A methodcalled ‘Static_Flow_Schedule’ is shown in FIG. 9A. This method can beused to select a flow-VOQ 106 to service, when the associated VOQ 16 isselected for service by the IP-controller 110. The method willeffectively schedule the packets in a traffic flow relatively evenlyover both halves of a time interval (a scheduling frame consisting of Ftime-slots), and this property will apply recursively. Therefore, thismethod will achieve a bounded NSLL for every flow departing a VOQ.

Referring to FIG. 7A, the flow-controller 102 may implement the methodStatic-Flow-Schedule shown in FIG. 9A. Consider a slotted IQ switch,where all packets have a maximum size. Assume the time axis is dividedinto scheduling frames, each consisting of F time-slots. The methodStatic-Flow-Schedule will compute a ‘flow-transmission-schedule’ foreach VOQ 16 in FIG. 7A. The flow-transmission-schedule will identify thetraffic flow-VOQ 106 to be serviced, for each time-slot in which theassociated VOQ 16 is enabled for service within a schedule frame. Theflow-transmission-schedule will remain constant, as long as all thetraffic rates of all the traffic flows associated with the VOQ 16 remainconstant. Whenever a new flow is added to a VOQ or a flow is removedfrom a VOQ, or the traffic rate demanded by a traffic flow changes, thenthe flow-transmission-schedule must be recomputed. While theflow-transmission-schedule remains unchanged, it may be computed once inthe flow-controller 102 and stored in controller 105. The controller 105can then control the flow-server 108.

Before examining FIG. 9, we first examine 2 methods shown in FIG. 8, toadd a traffic flow to a VOQ 16 and to remove a traffic flow from a VOQ16.

Methods Add_Flow, Remove_Flow

The MATLAB mathematical modeling language syntax is used. MATLAB is amathematical programming language developed by MathWorks, withheadquarters at Natick, Mass. 01760-2098, USA,http://www.mathworks.com/.

As described earlier, in a backbone router 12 as shown in FIG. 1A or 1B,a VOQ 16 may contain packets from thousands of provisioned trafficflows. In general, each input port 12 needs to maintain controllers, forexample the IP controller 110, the flow-controller 102 and the optionalcontroller 105, which keeps track of the provisioned traffic flows whichare associated with each VOQ 16. A method is needed to add a provisionedtraffic flow to a VOQ 16 in an input port 12. Another method is neededto remove a provisioned traffic flow from a VOQ 16 in an input port 12.

Referring to an input port 12 shown in FIG. 7A, the method Add_Flowshown in FIG. 8A can be used to add a provisioned traffic flow to a VOQ16 in the input port 12. Line 150 starts the method Add_Flow. Assumethat every flow is identified by a unique number called a label. Theparameter ‘label’ identifies the flow to be added, the parameter ‘rate’equals the traffic rate of the flow (expressed in a number of time-slotreservations per scheduling frame), and the parameter ‘voqn’ identifiesthe VOQ to which the flow is to be added. These 3 parameters areintegers. Line 152 declares a globally visible data structure calledVOQR. The number of flows associated with each VOQ 16 in the input port12 is stored in this data structure, as well as the list of flowsassociated with each VOQ 16.

Line 154 reads the data structure element VOQR(voqn) to retrieve thenumber of flows associated with VOQ(voqn) 16, and initializes a variable‘num_flows’ to equal this value. Line 156 updates the elementVOQR(voqn), to record the addition of a new flow. Line 158 adds thelabel of the flow to the list of flows associated with VOQ(voqn) 16, inthe element VOQR(voqn). Line 160 initializes the Flow_VOQ 106 with index‘label’ to be empty. Line 162 assigns a variable VFT(label) to equalinfinity. This variable VFT(label) is used in a subsequent method, andwill be discussed later.

The method Remove_Flow is shown in FIG. 8B, which removes a traffic flowfrom one VOQ 16 in an input port 12. Line 170 starts the methodRemove_Flow. The input parameters ‘label’, ‘rate’ and ‘vqon’ have thesame definitions as in method 8A. Line 172 declares the globally visibledata structure called VOQR. Line 174 decrements the number of flowsassociated with VOQ(voqn) 16, in the element VOQR(voqn). Line 178 causesthe flow with the given label to be removed from the list of flowsassociated with VOQ(voqn) 16 in the element VOQR(voqn). Line 180 setsthe Flow_VOQ 106 with index ‘label’ to be empty. Line 182 sets thevariable VFT(label) to be infinity. This variable VFT(label) is used ina subsequent method, and will be discussed later.

Method Static_Flow_Schedule.

The method Static-Flow-Schedule is shown in FIG. 9A. Assume an IQ switch10 as shown in FIG. 1A, using packets with a maximum size and ascheduling frame of length F time-slots. The method can also be used forthe switches in FIGS. 1B, 1C and 1D. This method will compute a vectorFVOQS which represents a flow-transmission-schedule, for one VOQ 16 inan input port 12. It will accept a binary VOQ-transmission-schedulevector VOQS, which indicates the time-slots in which the VOQ willreceive service. The method will process the list of flows associatedwith this VOQ, and will schedule the flows for service for thetime-slots when the VOQ receives service. The flow-transmission-schedulewill identify which flow-VOQ 106 to service, when a VOQ 16 is enabledfor service.

On line 200, the method accepts a vector ‘rate’, and a vector ‘VOQS’.The vector element rate(j) equals the rate of an active flow with labelj, expressed as a number of time-slot reservations in a scheduling frameof length F time-slots. The vector VOQS is the binaryVOQ-transmission-schedule. The vector element VOQS(ts) equals 1 if theVOQ 16 is scheduled for service in time slot ts. Line 200 will return avector FVOQS of length F, which identifies the flow to be serviced, forthe F time-slots in a scheduling frame. This schedule will only select aflow-VOQ 106 for service in a time-slot when the VOQ 16 is selected forservice.

Line 202 defines some globally visible parameters, the length of ascheduling frame F and the maximum number of flows NF. Line 204initializes the vector FVOQS to be a vector of zeros with length F. Line206 initializes a vector SP to be a vector of zeros with length NF.Element SP(j) indicates how many packets have been scheduled for theflow with label j. Line 208 initializes a vector VFT of length NF sothat all elements are infinity. VFT(j) represents the ‘Virtual FinishingTime’ of flow j.

Lines 210-219 will assign the VFT for the first packet associated witheach flow with a non-zero rate to be equal to the IIDT associated withthe flow, which equals F divided by the rate of the flow. Line 216indicates that the first packet of each such flow has been scheduled.Lines 220 to 246 define a second loop, which processes each time-slot tsin a scheduling frame of length F. Line 222 tests to see if the VOQ 106is scheduled for service in time-slot ts, in theVOQ-transmission-schedule. If true, lines 224-244 are performed. Line224 searches through the vector VFT, to find the flow with the minimumVFT value. The VFT with minimum value is stored in variable ‘minVFT’,and the index (or label) of the flow is stored in variable ‘flow’. Line226 tests to see if the minVFT is less than infinity. If true, lines228-242 are performed. Line 228 assigns the vector FVOQS(ts) to equalthe variable ‘flow’, thereby scheduling the flow with index ‘flow’ to beserviced in time-slot ts. Line 230 updates the VFT. The new VFT equalsthe current VFT plus the IIDT of the flow Line 232 tests to see if thenumber of scheduled packets for the flow is less than the rate of theflow. If true, then line 232 increments the vector element SP(flow)representing the number of packets already scheduled for service in thisflow. If line 232 is false, then line 238 sets the VFT of the flow to beinfinity since all its packets have been scheduled. As a result, no morepackets will be scheduled for this flow.

The vector FVOQS represents the flow-transmission-schedule, whichcontrols the flow-server 18 for each time-slot in a scheduling frame ofF time-slots. It identifies the flow-VOQ 106 to be serviced, when theVOQ 16 is enabled for service. The flow-transmission schedule willremain unchanged when the traffic flows not change. Therefore, it can becomputed and stored in the controller 105, and be re-used for severalscheduling frames, while the traffic flows do not change. When thetraffic flows change, the VOQ-transmission-schedule and theflow-transmission-schedule must be recomputed.

If variable-size packets are used, then line 230 which updates the VFTof a flow when the next packet is scheduled should be changed. The VFTof the next packet of the flow should equal the current VFT of the flowplus the length of the next packet in bits, divided by the weight of theflow. The method in FIG. 9B can be used to compute the weight of all theflows traversing one VOQ, with different rates.

The method in FIG. 9A can be modified in several ways, while stillguaranteeing a bounded NSLL for each flow. For example, the assignmentof the initial VFTs to traffic flows, in lines 210-219, can use otherinitial values. The method is also general and can be used to scheduleany type of time-slot requests, i.e., it is not constrained to scheduleonly flow-VOQs within a VOQ.

Method Static_Flow_Schedule_Realtime.

The method Static_Flow_Schedule_RealTime is shown in FIG. 9C. It is aslightly modified version of method Static_Flow_Schedule in FIG. 9A.This method can be used to schedule multiple flows for the special casewhen all time-slots are available to be used for scheduling, i.e., theinput vector VOQS is a vector of ones. The method in FIG. 9C willcompute a vector FVOQS which represents a flow-transmission-schedule,for one VOQ 16 in an input port 12. It will accept a binaryVOQ-transmission-schedule vector VOQS, which indicates the time-slots inwhich the VOQ will receive service (which are all ones). The method willprocess the list of flows associated with this VOQ, and will schedulethe flows for service. The flow-transmission-schedule will identifywhich flow-VOQ 106 to service.

Only the changes from the method in FIG. 9A will be described. Line 280computes the sum of all the packet transmission requests to be scheduledin the vector ‘rate’. Line 284 tests to see if the packet with thesmallest VFT can be scheduled in the current time-slot ‘ts’. Line 284also tests to see if the number of packet transmission requestsremaining to be scheduled in ‘Rsum’ equals the number of remainingtime-slots in the frame schedule. If either condition is true, then thepacket is scheduled for service in the current time-slot in lines85-292. Line 285 also increments the counter ‘Rsum’, to record the newlyscheduled packet.

The method in FIG. 9C can be modified in several ways, while stillguaranteeing a bounded NSLL for each flow. For example, the assignmentof the initial VFTs to traffic flows, in lines 270-279, can use otherinitial values.

Experimental Results, Method Static-Flow-Schedule

To gather results of this method, a computer simulation of a network wasperformed. The network consists of a linear chain of 10 IQ routers ofsize 4×4, where each link operates at 10 Gbps. A scheduling frame ofduration F=2048 time-slots was selected. Traffic flows were iterativelyadded and routed through the network in ‘phases’. In each phase, thecomputer program would visit every input port. At every input port, thecomputer program would attempt to add a new traffic flow, and to routethe traffic flow from that input port on the 1st switch, to a randomlyselected output port on the last switch. The rate of the traffic flowwould be randomly selected between 1 and 60 time-slot reservations perscheduling frame. If the flow could be successfully routed, the flowwould be added to the appropriate VOQ 16 in each router, and a flow-VOQ106 would be created for that flow. The phases were repeated, until thenetwork was 100% saturated. The resulting specification of multipletraffic flows, their sources, their destinations, their paths and theirrates, is called a ‘traffic specification’. The method in [18] was usedto compute the VOQ-transmission-schedules. The methodStatic_Flow_Schedule in FIG. 9 was then used to compute aflow-transmission-schedule, i.e., to schedule each flow-VOQ 106associated with a VOQ 16.

Several traffic specifications were generated and simulated, and alltraffic specifications yielded similar results. The results for oneparticular traffic specification are described next. There are 514traffic flows entering the first router, with an average of 128.5 flowsper input port 12, and with an average of 32.125 flows per VOQ. All 514traffic flows exited the last router, with an average of 128.5 flows peroutput port 14. Every input port 12 and output port 14 was 100% loaded.This traffic specification represents a very heavily loading of thenetwork, as every link and every router is operating at 100% of its peakcapacity.

Before entering the network, the traffic flows were shaped by a tokenbucket traffic shaper 82 to have a bounded NSLL<=1 packet. A similarcomputer model is described in the paper [18]. The network would then besimulated for several scheduling frames. Each scheduling frame had aduration of 2,048 time-slots. It would take several scheduling framesfor the network to reach equilibrium, as initially all the flow-VOQs 106are empty. After the network reached equilibrium, the network wassimulated for 4 scheduling frames, and various statistics were gathered.

FIG. 12 presents results for the method Static-Flow-Schedule shown inFIG. 9A. FIG. 12A illustrates the end-to-end delay for all 514 flows,expressed in terms of un-normalized time-slots. The end-to-end delayvaries from about 400 times-slots up to 2,048 time-slots. FIG. 12Billustrates the end-to-end normalized delay for all 514 flows, expressedin terms of normalized time. The normalized end-to-end time for a flowis the end-to-end time divided by the IIDT of the flow. The normalizeddelay varies from about 3 IIDT up to 10 IIDT, where the IIDT representsthe time between packet departures in a perfectly-scheduled trafficflow. FIG. 12C illustrates the variance in the end-to-end delay of all514 traffic flows leaving the network, expressed in time-slots. FIG. 12dillustrates the same data as in FIG. 12C, where the x-axis is nowexpressed in normalized time. Equivalently, FIG. 12D plots the varianceof the end-to-end delay of all 514 traffic flows leaving the network,expressed in terms of IIDT of each flow. As stated in the four theorems,the variance of the normalized delay is small and bounded by a few IIDT,and can be easily filtered out at a destination using a small playbackqueue of depth O(K) packets, to deliver a perfect zero-jitter stream ofnetwork-layer packets. To reconstruct variable-size application-layerpackets, a larger Application-Specific Playback Queue 88 must be used,as described in FIG. 5.

FIG. 12E illustrates the distribution for the number of packets in theflow-VOQs 106. There are 5,140 individual plots, where each plotrepresents one of the 514 flow-VOQs 106 in each of the 10 routers.Observe that every flow-VOQ 106 is small and bounded in size, to amaximum of 2 packets. FIG. 12F illustrates the distribution for thenumber of packets in the VOQs 16. There are 160 individual plots, eachplot representing one of the sixteen VOQs 16 in each of the 10 routers.Observe that every VOQ 16 has small and bounded in size, to a maximum of35 packets. Each VOQ 16 supports on average 32.125 traffic flows, i.e.,each VOQ 16 has 32.125 active flow-VOQs 106 on average, and each VOQ 16contains a maximum of 35 packets in this computer simulation.

Note that the method Static-Flow-Schedule in FIG. 9A has allowed trafficflows to be transmitted across the network with a bounded NSLL, whilethe network operates at 100% load. To transmit application-layer packetsacross the network with bounded router buffer sizes and QoS guarantees,an Application-Specific Traffic Shaper 82 can be used at each sourcenode 93, and an Application-Specific Playback Queue 88 can be used ateach destination node 99. Therefore, a busty application-layer trafficflow can be transmitted across the network and regenerated at thedestination with strict Quality of Service guarantees, as described inFIG. 5.

A Method for Dynamic Flow-Schedules

A work-conserving queueing system is defined as a queueing system inwhich the server will never be idle when there is a packet in the queue.Equivalently, a server will always be serving a packet as long as thereare packets in the queue. The method Static-Flow-Schedule in FIG. 9A isnot work-conserving. Referring to FIG. 7A, suppose the VOQ 16 hasseveral non-empty flow-VOQs 106, but the next flow-VOQ 106 selected forservice in the method Static-Flow-Schedule is empty. The flow-server 108and the VOQ-server 18 will both remain idle even when the selected VOQ16 is non-empty, violating the definition of a work-conserving queuingsystem. A work-conserving queueing system should have smaller queuesizes on average, compared to a non-work-conserving system. Topotentially improve the performance, consider a methodDynamic-Flow-Schedule shown in FIG. 10.

A method to dynamically compute a schedule for the flows-VOQs ispresented. The method is based upon the theory of GPS/WFQ developed byParekh and Gallager in [1] and [2]. In the dynamic method, the arrivaltime of a packet at a VOQ 16 will determine its Virtual Finishing Time(VFT) and its departure order from the VOQ 16. When packet k of flow farrives at a non-empty or empty VOQ 16, the GPS/WFQ theory provides thefollowing 2 equations, equation 1 and equation 2, to determine itsvirtual finishing time, when packets can have variable sizes:

VFT(k,f)=VFT(k−1,f)+B(k,f)/W(f)  (1)

VFT(k,f)=cVT+B(k,f)/W(f)  (2)

B(k,f) denotes the number of bits in packet k of flow f, and W(f) is theweight of the flow.

In our input port 12 shown in FIG. 7A, when the VOQ 16 is enabled toserve a packet, it selects a packet from the flow-VOQ 106 with thesmallest VFT.

Referring to the input port 12 in FIG. 7A, when an input port 12receives an arriving packet, the flow-controller 102 forwards the packetto the appropriate flow-VOQ 106, and updates its internal state. Theflow-controller 102 maintains the number of packets in each flow-VOQ106, and it computes the VFT of each packet as it arrives. TheVOQ-server 18 will be activated according to the IP-controller 110. TheIP-controller will control the VOQ-server 18 to select a given VOQ 16 ineach time-slot. In the dynamic flow-scheduling method, theflow-controller 102 will control the flow-server 108 associated with theVOQ 16, to select an appropriate flow-VOQ 106 to service dynamically,when the VOQ server 18 is enabled.

The flow-controller 102 can select a flow-VOQ within the VOQ to servicedynamically by calling the method Dynamic_Rem_Packet in FIG. 10B.

The flow-controller 102 may implement the methods Dynamic_Add_Packet inFIG. 10A and the method Dynamic_Rem_Packet in FIG. 10B. Consider first aslotted switch, where all packets have a maximum size. Assume the switchoperates according to scheduling frames, each consisting of Ftime-slots.

The method Dynamic_Add_Packet is shown in FIG. 10A. This method is usedto add an arriving packet to a flow-VOQ 106. The input variable ‘flow’equals the label of the flow, and the variable ‘voqn’ identifies the VOQ16 which contains the flow-VOQ 106. Line 302 defines some globallyvisible numbers, the length of a scheduling frame F, the maximum numberof flows NF, and the current virtual time (cVT). Line 304 defines someglobally visible data structures. Flow_VOQ is a vector which records thenumber of packets stored in each flow_VOQ 106. pVFT is a matrix with Frows and NP columns, representing the VFTs assigned to the packetsassociated with each flow, over a window of NP packets, where NP is thenumber of packets in the window. The virtual finishing time of everypacket in every flow is computed and stored here, over a window of time.The SP is a vector recording the number of packets already scheduled(i.e., assigned a VFT) for every flow. The Rate is the vector of trafficrates for each flow, where each rate is expressed in time-slotreservations per scheduling frame of length F time-slots.

Line 306 initializes the variable ‘pkt’ to be the number of the packetadded to this flow-VOQ 106, and it increments the vector elementSP(flow) to reflect that this packet has been scheduled (i.e., assigneda VFT). Line 308 tests to see if the flow_VOQ 106 for the current flowis empty. If true, then line 310 is processed, which assigns a VFT to apacket arriving at an empty flow-VOQ. Line 310 assigns the packet a VFTequal to the current virtual time cVT plus the IIDT of the flow. Thispacket's VFT value is recorded in the matrix element pVFT(flow,pkt). IfLine 308 is false, then line 316 is processed. Line 316 computes the VFTof the packet arriving at a non-empty flow-VOQ, which equals the VFT ofthe packet ahead of it in the flow_VOQ 106, plus the IIDT of the flow.This value is recorded in the matrix pVFT(flow,pkt). The method can beadapted to use variable-size packets and unslotted switches. Ifvariable-size packets are used, the IIDT is replaced by the length ofthe packet in bits divided by the weight of the flow.

FIG. 10B illustrates the method Dynamic_Rem_Packet. The input parameter‘voqn’ identifies the VOQ 16 from which a packet is to be removed. Thismethod is called when a VOQ 16 is scheduled for service by the IPcontroller 110, and a flow-VOQ 106 must be selected for service. Line332 lists some globally visible data-structures. SP is a vector whichrepresents how many packets have been scheduled for each flow. VOQR is adata-structure recording the number of flows associated with each VOQ16, and the list of flows associated with each VOQ 16. pVFT is thematrix of packet VFTs for every flow. Flow_VOQ is a vector representingthe number of packets stored in each flow-VOQ 106. Line 336 retrievesthe list of flows associated with the VOQ 16, from the data-structureelement VOQR(voqn). Line 338 retrieves the number of flows associatedwith the VOQ 16. Line 340 initializes 3 variables to be infinity. Lines342 to 352 form a loop, which processes every flow in the list of flows.Line 344 retrieves the label of the next flow in the list of flows andassigns it to variable ‘flow’. Line 345 finds the minimum VFT of anypacket associated with this flow which is still in the flow-VOQ. Theminimum VFT value is stored in ‘fvft’, and the packet number is storedin ‘pkt’. Line 346 tests to see if the minimum VFT in ‘fvft’ is lessthan the current minimum VFT in variable ‘minVFT’. If true, then line348 will record the new minimum value of the VFT in variable ‘minVFT’,it will record the label of the flow in variable ‘minf’, and it willrecord the packet number in variable ‘minpkt’. After the loop has beencompleted, line 354 tests to see if the variable ‘minVFT’ is less thaninfinity. If true, then a flow-VOQ 106 containing a packet with theminimum VFT has been selected. In line 356, the value ‘minf’ is assignedto variable ‘flow’, the value ‘minpkt’ is assigned to ‘pkt’, which willbe returned by the function. In line 356, the VFT stored in the matrixelement pVFT(flow,pkt) is reset to infinity, so that the packet will notbe selected again. The label ‘flow’ returned by the function can be usedto control the flow-server 108 to select a flow-VOQ 106 for service.

Excess Bandwidth Sharing

One property of the GPS/WFQ theory and the methods Dynamic_Add_Packetand Dynamic_Rem_Packet in FIGS. 10A and 10B is that any excess bandwidthon a link is shared amongst all non-empty flows. Excess bandwidth isdefined as bandwidth which is un-reserved by any provisioned trafficflows. Therefore, a non-empty flow-VOQ 106 may receive more than itsfair share of service over a short interval of time, if the link hasexcess bandwidth, as that excess bandwidth will be allocated to theflows with packets. Therefore, even if an arriving traffic flow has abounded NSLL<=K, the departing traffic flow may have a NSLL which isgreater than K over a short interval of time, and theorems 1-4 do notstrictly apply.

In other words, a flow-server 108 using the methods Dynamic_Add_Packetand Dynamic_Rem_Packet in FIG. 10A may not guarantee that everydeparting traffic flow has a bounded NSLL<=K, for some small integer K.Once one traffic flow looses this property, it may cause other trafficflows to loose the same property, and the entire network may deteriorateto the case were many traffic flows have lost the property that NSLL<=K.Once flows loose this property, the queues may grow to be quite large,packets may be dropped due to queue overflow, the end-to-end delaycannot be guaranteed, and the Quality of Service for any traffic flowscannot be guaranteed. It should be noted that provided each traffic flowis shaped before entering the network to have a NSLL<=K, for someinteger K, then the NSLL at any router using the methodsDynamic_Add_Packet and Dynamic_Rem_Packet might still be bounded, butthe bound may be larger than K, i.e., it may be 10*K or 50*K. Thisincrease in the NSLL will cause the buffers in the switches or routersto hold many more packets than necessary, and it may cause the loss ofpackets due to buffer overflow. This effect is especially important forall-optical packet switches, where the size of the buffers in theswitches should be kept to a very small number.

In addition to the above issue, the methods Dynamic_Add_Packet andDynamic_Rem_Packet can suffer from another potentially serious problem.A malicious user could inject a traffic flow without a bounded NSLL intothe network. The work-conserving flow-servers 108 may propagate thismalicious flow without a bounded NSLL, causing other flows to loosetheir small bounded NSLL which should be <=K. Once again, once a singleflow looses this property, it may cause other flows to loose thisproperty, and the network can deteriorate to the case where many flowshave lost this property and where QoS guarantees can no longer be made.To avoid this potentially serious deterioration, work-conservingflow-servers 108 should use extra processing in each router, to ensurethat traffic flows departing a router have a bounded NSLL<=K. (Not everyrouter must ensure the bounded NSLL, but periodically some routersshould re-shape the traffic to have a bounded NSLL.) For example, eachinput port 12 could contain a token bucket traffic shaper 82 asdescribed in FIG. 4A, for every flow-VOQ 106. The token bucket trafficshaper 82 will ensure that no flow exceeds its bound on the NSLL.

Method to Disable Excess Bandwidth Sharing

Alternatively, the method Dynamic_Rem_Packet in FIG. 10B can bemodified, to disable the excess bandwidth sharing property of theGPS/WFQ algorithm (at least in some routers). Recall that the functionDynamic_Rem_Packet removes a packet for service from a VOQ 16. In line346 it selects the flow-VOQ with the smallest VFT(virtual finishingtime) to service. In line 354 it returns the flow label ‘flow’ as longas the flow-VOQ is non-empty, i.e., as long as the ‘minVFT’ is less thaninfinity. To disable the excess bandwidth sharing, a few lines in thesemethods must be modified.

Line 310 in FIG. 10A should be replaced by line 325. Line 325 replacesthe variable current virtual time (cVT) by the current real time (cRT).The current real-time is the number of the current time-slot. Assumetime-slots are numbered by consecutive integers, starting at time-slot 0at time 0. Each input port 12 must have a time-clock to record thereal-time, rather than virtual time, and cRT denotes the current valueof the real-time clock, measured in time-slots. The real time is similarto the virtual time, except it is not virtual and it is measured intime-slots. In a system with fixed-sized packets, the real time keepstrack of the current time-slot. In FIG. 10A, line 310 assigns a flow-VOQa virtual finishing time when a packet arrives to an empty flow-queue,and the VFT is based upon the current virtual time plus the IIDT. Incontrast, line 325 assigns a flow-VOQ a VFT when a packet arrives to anempty flow-queue, where the VFT equals the current real-time plus theIIDT.

To disable bandwidth-sharing, line 354 in FIG. 10B should also bereplaced, by the new line 370 shown in FIG. 10B. This new line 370ensures that a flow-VOQ is selected for service only if its VFT isgreater than the current value of the real-time clock cRT. The line 354can also be replaced by line 372, which allows the methodDynamic_Rem_Packet to remove a packet with a slight service lead,determined by the variable X. For example, X may be between zero and oneIIDT, which allows packets to depart with a slight service lead.

Experimental Results for Dynamic Flow Scheduling Method

FIG. 13 presents results for the methods Dynamic_Add_Packet andDynamic_Rem_Packet. FIG. 13A illustrates the end-to-end delay for all514 flows, expressed in terms of time-slots. The delay varies from about1 up to 2,048 time-slots. FIG. 13B illustrates the normalized end-to-enddelay. The normalized end-to-end delay is reduced somewhat compared toFIG. 12A. FIG. 13C illustrates the variance in the end-to-end delay ofall 514 traffic flows leaving the network. FIG. 13D illustrates thevariance in the end-to-end normalized delay of all 514 traffic flowsleaving the network. The variance of the normalized delay is still smalland bounded, and can be easily filtered out with a small playback queue.FIG. 13E illustrates the distribution of the number of packets in theflow-VOQs 106. Observe that every flow-VOQ 106 is small and bounded insize, to a maximum of 2 packets. FIG. 13F illustrates the distributionof the number of packets in the VOQs 16. Observe that every VOQ 16 isbounded in size, with a maximum size of about 18 packets. The methodsDynamic_Add_Packet and Dynamic_Rem_Packet have reduced the maximum VOQ16 size, from about 35 packets using the method Static Flow Schedule inFIG. 9A, to about 18 packets. To guarantee that a departing flow has abounded NSLL<=K, the traffic shapers can be added as explained earlier,or the modified methods Dynamic_Add_Packet and Dynamic_Rem_Packet withthe disabled bandwidth-sharing property in FIG. 10 are used.

A Method for a Random Flow Schedules

Consider a method for randomly scheduling the flows within a VOQ, whenthe VOQ is enabled for service. Referring to FIG. 7A, when a VOQ 16receives service, any non-empty flow-VOQ 106 is selected at random toreceive service. This VOQ-server is clearly work-conserving.

Referring to FIG. 7A, the flow-control module 102 maintains the numberof packets in each flow-VOQ 106. The VOQ-server 18 will be activated bythe IP-controller 110, and the IP-controller will control the VOQ-server18 to select a specific VOQ 16 for service. The flow-controller 102 willcontrol the flow-server 108 associated with the VOQ 16, to select anappropriate flow-VOQ 106 to service, when the VOQ-server 18 is enabled.

The flow-controller 102 may implement the methods in FIGS. 11A and 11B.FIG. 11A illustrates the method Rand_Add_Packet. The input parameterflow equals the label (unique identifier) of the flow. The inputparameter ‘pkt’ equals the packet number if the arriving packet. Line372 identifies the flow_VOQ data-structure as visible. Thisdata-structure now stores the list of packets which are queued in theflow-VOQ 106. Line 374 adds the packet with identifier ‘pkt’ to the endof the list of packets in the flow-VOQ 106 for the flow.

The method Rand_Rem_Packet is shown in FIG. 11B. The input parameter‘voqn’ identifies the VOQ 16 from which a packet is to be removed. Line397 Indicates that the VOQR and flow-VOQ data-structures are visible.Line 380 retrieves the list of flows associated with the relevant VOQ16. Line 382 retrieves the number of flows associated with the relevantVOQ 16. Line 384 generates a random permutation of the numbers startingfrom 1 and ending at num_flow. The flow_VOQs 106 will be examined in arandom order determined by this permutation. Lines 386 to 396 form aloop using parameter j. Line 388 identifies the next unexamined flow-VOQ106. Line 390 tests to see if the flow_VOQ is non-empty. If true, line392 removes the head-of-line packet from the flow_VOQ and stores it invariable ‘pkt’. Line 394 causes the method to return the packet and theflow identifier. The loop is processed until all flow-VOQs 106 have beenexamined, If all flow_VOQs 106 are empty, line 397 assigns the variables‘flow’ and ‘pkt’ to be −1, which indicates that all flow-VOQs 106 areempty, and the method returns these values. These variables are used bythe flow-server 108 to select a flow-VOQ 106 for service, when theassociated VOQ 16 is selected for service by the IP controller 110.

While the method Rand_Rem_Packet illustrates as a series of processingsteps, the method can be easily implemented in hardware. A hardware treeof binary nodes can be created. The tree has enough binary nodes at thebottom level to process all flows. The tree has one output at the top,which returns the label of a non-empty flow-VOQ selected at random. Eachbinary node examines two flow_VOQs 106 at its bottom level, selects anon-empty flow-VOQ at random, and propagates the flow-VOQ identifier upthe tree. Such a tree is straight-forward to design in hardware.

The methods Rand_Add_Packet and Rand_Rem_Packet may lower the averagenumber of packets queued per flow-VOQ 106 per router compared to themethod Static_Flow_Schedule, since it is work-conserving. However, it isalso expected to increase the worst-case flow-VOQ queue sizes, and italso has the side-effect of no longer guaranteeing that every flow has aNSLL<=K, just as the methods using dynamic Flow-Scheduling.

FIG. 14 presents results for the methods Rand_Add_Packet andRand_Rem_Packet. FIG. 14A illustrates the end-to-end delay for all 514flows. The end-to-end delay has a smaller maximum compared to FIG. 12A,and the maximum delay is about 1000 time-slots. FIG. 14B illustrates thenormalized end-to-end delay of all 514 traffic flows leaving thenetwork. The normalized delay is slightly larger compared to FIG. 12A,but it still small and bounded provided that every traffic flow isshaped to have a bounded NSLL at the entry point to the network, and canbe filtered out. FIG. 14E illustrates the distribution of the number ofpackets in the flow-VOQs 106. Observe that the maximum flow-VOQ size islarger, close to 10 packets. The methods for random flow scheduling haveincreased the maximum size of the flow-VOQs 106, as expected. FIG. 14Fillustrates the distribution of the number of packets in the VOQs 16.Observe that every VOQ 16 is bounded in size with a maximum of 32packets. The methods for random flow scheduling have a reasonably goodaverage performance, according to these computer simulations, but theyhave poor worst-case performance. If these methods are used in routers,then the traffic should be periodically re-shaped in some other routersto achieve a bounded NSLL.

Large Normalized Service Lead/Lag

FIG. 15 presents the results of the methods for random flow scheduling,when the traffic flows are injected into the network with a larger butbounded NSLL of <=20 packets. Each switch uses the random flowscheduling methods in FIG. 11A and FIG. 11B, which do not minimize theNSLL. FIG. 15A illustrates the end-to-end delay for all 514 flows. Themaximum end-to-end delay is approximately 8000 time-slots. FIG. 15Billustrates the normalized end-to-end delay of all 514 traffic flowsleaving the network. The maximum normalized delay is now about 80 IIDT,considerably larger than the prior methods. FIG. 15E illustrates thedistribution of the number of packets in the flow-VOQs 106. Observe thatthe maximum flow-VOQ size is about 200 packets. FIG. 15F illustrates thedistribution of the number of packets in the VOQs 16. Observe that themaximum VOQ 16 size is approximately 500 packets. This exampleillustrates several points. When traffic flows are injected into thenetwork with a larger NSLL, even 20 packets, the large bound on the NSLLwill increase the buffer sizes in all the switches. In this particularexample, each switch selects packets to serve at random, which does notminimize the NSLL. To achieve very small and bounded buffer sizes inevery switch, the injected traffic flows should have small and boundedNSLL, and each switch should schedule traffic flows using thenon-work-conserving methods which tend to minimize the NSLL.

In some applications, allowing a larger NSLL such as 25 or 50 packetsmay be acceptable, and allowing the VOQ 16 buffer sizes in the switchesto be large enough to accommodate for example 1000 or 10,000 packets maybe acceptable. These maximum sizes are still several orders of magnitudesmaller than the buffer sizes used in current Internet routers. Theimportant point is that network designers now have a theory fordesigning buffers in networks. They can now choose the acceptable NSLLbounds, and then design the router buffer sizes accordingly, which wasnot possible previously.

Other Flow Scheduling Methods

The flow-server 108 can select flow-VOQs 106 in a VOQ 16 for service inseveral other orders, including: Oldest Cell First (OCF), LargestFlow-Queue First (LFQF), Largest Rate First, round-robin, etc, withsimilar performances. For example, the Largest Flow-Queue First (LFQF)algorithm could select the flow-VOQ to service with the largest numberof queued packets, whenever the VOQ is scheduled for service.

FIG. 15 also illustrates another useful property for network design.Traffic can be reshaped to have a small and bounded NSLL at selectedswitches or routers within the network, rather than in every router.Every switch or router need not achieve a small and bounded NSLL. Letthe switches or routers in a network belong to 2 classes, thetraffic-shaping class of routers and the non-traffic-shaping class. Therouters in the traffic-shaping class will shape provisioned trafficflows using non-work-conserving schedulers, to achieve a bounded NSLL.The routers in the non-traffic-shaping class will not shape provisionedtraffic flows, and may use work-conserving schedulers which do notguarantee a bounded NSLL for the provisioned traffic flows. The sizes ofthe VOQs 16 in the routers will increase as the bound on the NSLL grows,but the traffic can be reshaped periodically and the bounds on the NSLLcan be reduced to acceptable limits, so that all VOQs 16 can be designedwith a known upper size, and strict QoS guarantees can still beachieved. Existing IP networks often use periodic traffic-reshaping inselected routers. For example, in the current Internet, DiffServ trafficentering a Differentiated Services domain is typically policed or shapedon entry to the domain to have a maximum burst size. These maximum burstsizes are typically very large. Once the traffic has entered a DiffServdomain, it moves between routers without being reshaped. Existinginternet routers are unaware of the concept of the NSLL and they do notguarantee a bounded NSLL. To achieve bounded router buffer sizes andstrict QoS guarantees for provisioned traffic flows, the internetrouters can be re-programmed to implement traffic shaping with a boundedNSLL on the provisioned traffic flows, periodically (or in everyrouter).

Traffic Matrix Examples

FIG. 16 illustrates several examples of these prior scheduling methods,used to generate the results for FIG. 12. To generate FIG. 12, acomputer simulation of a saturated network was performed. The networkhad 10 input-queued switches in a linear array, each of size 4×4. Thescheduling frame had a duration of F-2048 time-slots. FIGS. 16A and 16Billustrates 2 traffic rate matrices T which specify the traffic rates tobe supported by the first two 4×4 input queued switches as shown in FIG.1A. Observe that the sum of every row and every column=2,048, i.e.,every input link and every output link is 100% utilized in everytime-slot in the scheduling frame. The first element T(1,1) of matrix Tin FIG. 16A has rate 490, which represents the sum of the traffic ratesof all flows traversing VOQ(1,1). FIG. 16C illustrates theVOQ-transmission-schedules computed for the first input queued switchwith the traffic rate matrix T in FIG. 16A. Each row represents aVOQ-transmission-schedule for one input port 12. In each row and in eachtime-slot, each input port 12 j with index j, for 0<=j<4, is connectedto one output port 14 k with index k, for 0<=k<4. The connections areshown only for the first 8 time-slots out of 2,048 time-slots. (TheseVOQ-transmission-schedules must be modified slightly for use in themethod of FIG. 9A, which requires a VOQS schedule as a binary vectorinput).

FIG. 16D illustrates the 33 flows which are associated with VOQ(1,1) inthe first input queued switch 10 with the matrix T in FIG. 16A. Thereare a total of 514 traffic flows, and each traffic flow is identified byan integer between 1 and 514.

FIG. 16E illustrates the flow-transmission-schedules, computed using themethod Static-Flow-Schedule in FIG. 9A, for each input port 12 in thefirst switch 10. Each row represents the flow-transmission-schedule forone input port. The flow-transmission-schedule indicates the flow-VOQ tobe served in each time-slot, by the flow-server.

Traffic Aggregation and MPLS Networks

In this section, we explore the buffer requirements for aggregatedtraffic flows in a hierarchical network. Networks are often organized inhierarchies, with local area networks, metro-area networks, andwide-area networks. Referring to FIG. 7A, a VOQ 16 in a wide areabackbone network may support potentially thousands of distinct trafficflows without aggregation. It is desirable to aggregate traffic flows atone level of the hierarchy, before injection into the next higher level.

FIG. 17A illustrates a routing table, which can be used in the routingmodule 20 in an input port 12 of the switch in FIG. 1A. Assume that eachtraffic flow passing through one VOQ 16 is identified by 2 uniquenumbers, the incoming label, and the outgoing label. In a typical MPLSnetwork, a packet arrives on an incoming link with an incoming label.This incoming label is used to read a routing table, as shown in FIG.16A. The routing table will indicate the new outgoing label for thetraffic flow, and the output port.

In the table in FIG. 17A, each row represents one traffic flow. Thereare 4 columns for each flow. The column LABEL-IN identifies the incominglabel, the column LABEL-OUT identifies the outgoing label, the columnOP-PORT identifies the outgoing output port 14 in FIG. 1A, and columnRATE identifies the rate of the traffic flow. In this example, the rateis expressed as a number of time-slot reservations in a scheduling frameof length F time-slots.

In the table in FIG. 17A, three traffic flows with incoming labels 27,130 and 94 all pass through the same VOQ 16 since they have a commonoutput port with label 1. Without any aggregation, each traffic flow istreated as an independent traffic flow, and has its own flow-VOQ 106 asshown in FIG. 7A. In FIG. 7A, each flow is scheduled separately by theflow-controller 102. Each flow also receives its own unique outgoinglabel.

With aggregation, all 3 traffic flows with incoming labels 27, 130 and94 can be aggregated to be treated as one logical flow on the outgoinglink of this router and in the following routers. In FIG. 17B, all threetraffic flows are assigned the same outgoing label, 103. In thefollowing routers, the traffic flow with incoming label 103 is treatedas one logical flow with rate 45+25+35=105. In the following routers,the aggregated traffic flow can use one flow-VOQ 106, and the aggregatedtraffic flow is scheduled as one flow with a higher rate of 105time-slot reservations per scheduling frame.

When packets from multiple traffic flows are aggregated into one flowwithout any buffering, it can be shown that the new bound of the NSLL ofthe aggregated flow is the sum of the bound on the NSLL for each flow.For example, the aggregation of 100 flows, each with a bounded NSLL<=Kpackets, may result in a new flow where the bound on the NSLL is 100*Kpackets. This large bound on the NSLL will result in larger queues, andtherefore it is desirable to bound the NSLL of the aggregated flow tosome integer K.

Therefore, when multiple flows are aggregated into a singleaggregated-flow care should be taken to ensure a bounded NSLL. Onemethod to aggregate multiple flows while maintaining a bounded NSLL<=Kis to use a token bucket traffic shaper 82 as shown in FIG. 4A for eachflow being aggregated. The capacity of the token bucket queue 84determines the allowable burstiness for any one flow, and determines thebound on the NSLL. This case is illustrated in FIG. 17C. FIG. 17Cillustrates an input port 12 for the router in FIG. 7A. In FIGS. 1A and7A, each VOQ 16 has an associated VOQ-module 100.

In FIG. 17C, the flows in the VOQ module 100 each have a traffic shapermodule 400. Each traffic flow entering a flow-VOQ 106 is first shaped bya traffic shaper 400, which redistributes any incoming bursts of packetsover a longer time interval. The traffic shaper 400 will prevent burstsof packets associated with any one traffic flow from propagating throughthe network, and will lower the NSLL.

An alternative embodiment of a VOQ-module 100 as shown in FIG. 17C isshown in FIG. 17D. In FIG. 17D, each VOQ-module 100 now has severalaggregation modules 109. Each aggregation module 109 consists of severalflow-VOQs 106, an aggregation server 107, and a token bucket trafficshaper 400. Traffic flows entering the input port 12 are forwarded tothe appropriate VOQ-module 100 associated with the desired output port14 by the server 15, as shown in FIG. 17C. As stated earlier, theflow-controller 102 processes the packets to determine which flow theybelong to, and controls the flow-demultiplexer 104 to forward thepackets to the appropriate flow-VOQs 106. In FIG. 17D, the flow-VOQs areorganized into regular flow-VOQs, and into flow-VOQs which reside in anaggregation module 109. The traffic flows which are to be aggregatedinto one flow are forwarded to flow-VOQs in an aggregation module 109.The aggregation module 109 combines the packets using an aggregationserver 107. The aggregation server 107 provides each flow-VOQ with fairservice, and adds their packets into the traffic shaper 400. Theaggregation server 107 is controlled by a controller, which may be theflow-controller 102. The aggregation server 107 can be controlled by themethod Static Flow Schedule in FIG. 9A, or the dynamic flow-schedulingmethods in FIGS. 10A and 10B with bandwidth-sharing disabled, which willminimize the NSLL. In the traffic shaper 400, packets are served intheir order of arrival. The token bucket traffic shaper 400 can onlytransmit a packet when it is selected by the server 108, and when it hassufficient tokens to enable the packet to be transmitted. Packets whichdepart the traffic shaper 400 will therefore have a bounded maximumNSLL.

The aggregation server 107 is logically no different from the VOQ-server18 or the flow-server 108 in FIG. 7A. Therefore, each flow beingaggregated will require a flow-VOQ 106 with capacity O(K) cells. Onceagain, it is convenient to visualize each flow as having its own virtualflow-VOQ 106 in the aggregation module 109, but the memory for theseflow-VOQs may be common and shared, just as the flow-VOQs 106 can belogical abstractions and can be maintained using pointers to a commonmemory. The aggregation server 107 can use any of the flow schedulingmethods examined earlier. It can use the method Static Flow Schedule inFIG. 9A, or it can use the dynamic flow scheduling methods in FIGS. 10Aand 10B with bandwidth-sharing disabled, to minimize the NSLL. It canalso use other methods such as the random flow scheduling method,Longest-Queue-First, Oldest-Cell-First, etc, although these will notminimize the NSLL and may lead to an unbounded NSLL.

Traffic aggregation can happen hierarchically, so that traffic flows canbe aggregated to create aggregated traffic flows with one level ofaggregation. However, these aggregated traffic flows can be furtheraggregated in other routers. Therefore, in a backbone InternetProtocol/MPLS network, there may a relatively small number ofhighly-aggregated traffic flows between a pair of cities, rather than avery large number of unaggregated traffic flows between the same pair ofcities.

Networks can often be viewed in a hierarchy, with local area networks,metropolitan area networks, and wide area (i.e., backbone) networks. Atraffic flow may originate in a local area network in one city, it maytraverse the backbone network, and be delivered to a local area networkin another city. At the backbone level, the traffic flow may be viewedas originating at a source node and terminating at a destination nodewithin the backbone network. The traffic flow may be injected into thelocal area network without a bounded NSLL, and it may be shaped at thesource node when it enters the backbone network to have a bounded NSLL.Similarly, the traffic flow may be delivered over the backbone networkwith a bounded NSLL, and it may be delivered over the destination localarea network with an unbounded NSLL. In this manner, a traffic flow mayuse a bounded NSLL within a backbone network at one level of thehierarchy, and it may use an unbounded NSLL at a lower level of thehierarchy. This hierarchical technique will allow many computers andservers to use the bursty TCP flow-control methods at a local areanetwork level. This hierarchical technique will allow routers to achievebounded buffer sizes, higher capacities and strict QoS guarantees at thehigher levels of the hierarchy.

The previous discussion allows for several traffic flows to beaggregated into single flows with higher rates. These aggregated trafficflows can be routed and scheduled through a network, to achieve boundedrouter buffer sizes and strict Quality of Service guarantees. The nextsection will present an alternative method to achieve bounded buffersizes and strict QoS guarantees, which requires less processing in therouters.

Traffic Classes and the Diffserv Model

Much of the existing Internet relies upon the Differentiated Services(DiffServ) service model, which is described in [3] on pages 717-722.This (DiffServ) model allows for several prioritized or differentiatedtraffic classes in a router. Let the traffic flows between source anddestination nodes be assigned a traffic class. For example, theDifferentiated Services model currently used by many routers has 3 maintraffic classes, the ‘Expedited Forwarding’ (EF) traffic class, the‘Assured Forwarding’ (AF) traffic class, and the ‘Best-Effort’ (BE)traffic class. The DiffServ model also allows several sub-trafficclasses, within each main traffic class. Several sub-classes in the AFclass are differentiated by their ‘drop-precedence’, i.e., how importanttheir packets are, which can be used when packets are dropped due tocongestion.

To include traffic classes in an input port 12 as shown in FIG. 1A,separate virtual output queues can be created for each traffic class.For example, a router may have 3 main traffic classes associated witheach VOQ, corresponding to the DiffServ EF, AF and BE traffic classes.(A router could have several more traffic classes.) Traffic for eachclass is forwarded into the appropriate traffic-class-VOQ, which isanalogous to the flow-VOQ. The traffic-class-VOQs may be quite large, asthe traffic from potentially hundreds or thousands of flows may beassigned to the same traffic-class-VOQ. The router is simplified sinceit no longer distinguishes significantly between the flows or packetswithin the same traffic-class-VOQ.

Consider the Input Port 12 shown in FIG. 18A. The input port 12 consistsof a router controller 20, a VOQ-demultiplexer 15, several traffic-classmodules 410, several VOQs 16, a VOQ-server 18 and an input portcontroller 110.

In FIG. 18A, arriving packets are processed by the router controller 20,which examines the packet header to determines the appropriate outputport 14 and the traffic class (if any) of the packet. Each VOQ 16 has anassociated traffic-class module 410, which stores the DiffServ packetsassociated with the VOQ 16. Each traffic-class module 410 consists of acontroller 402, a class-demultiplexer 404, several traffic-class-VOQs406, zero or more regular flow_VOQs 106, a class server 420 and acontroller 421. One traffic-class-VOQ 406 may contain packets fromhundreds or thousands of different traffic flows, and these packets allhave a common DiffServ traffic class, for example EF, AF or BE. When apacket arrives at the input port 12, its header is examined in routermodule 20, and it may be forwarded by the demultiplexer 15 to theappropriate traffic-class module 410 associated with a VOQ. Trafficflows and traffic classes which are associated with one VOQ and whichhave bandwidth provisioned for them are routed to thetraffic-class-module 410. When a VOQ 16 receives service from the inputport controller 110 according to the VOQ-transmission-schedule, thetraffic-class module 410 associated with the VOQ 16 is activated toselect a packet to serve, from all the traffic-class-VOQs and theflow-VOQs. The class controller 402 will process the status of thetraffic-class-VOQs 406 and the flow_VOQs 106, to determine which VOQ andpacket to select for service, and control the server 420.

There are several methods in which a class server 420 can select a VOQand packet for service, when it is enabled for service. The methodStatic-Flow-Schedule in FIG. 9A can be used to schedule traffic classesand traffic flows. The method will guarantee a bounded NSLL for anaggregated traffic class leaving the routers and a flow-VOQ leaving therouter. If static methods are used, the schedules can be loaded into thecontroller 421 which can control the server 420, until the schedules arerecomputed. Alternatively, the methods which dynamically schedule a flowfor service in FIGS. 10A and 10B can be modified slightly to considerboth traffic-class-VOQs and flow_VOQs and can be used. The dynamicflow-scheduling methods had 2 options, where the excess bandwidthsharing property is enabled or disabled. If the excess bandwidth sharingproperty is enabled, then these dynamic flow scheduling methods mayresult in a larger NSLL for the total traffic of traffic class, and foreach flow in a flow_VOQ. This increase in the bound on the NSLL may beundesirable, unless the traffic is shaped periodically in other routers.If the excess bandwidth sharing property is disabled, then the dynamicflow scheduling methods will result in a bounded NSLL for the totaltraffic of a traffic class leaving the router, and a bounded NSLL foreach flow leaving a router.

Another method to ensure a bounded NSLL for each traffic class, we mayadd a token bucket traffic shaper 408 to each class of traffic, andpotentially to each flow_VOQ 106, as shown in FIG. 18B. The token buckettraffic shapers 408 are based on the design in FIG. 4A. The methodStatic-Flow-Schedule in FIG. 9A can be used to schedule traffic classesand traffic flows by the class controller 402 in FIG. 18B.Alternatively, the methods for dynamically scheduling a traffic flow inFIGS. 10A and 10B can be modified to include both traffic classes andtraffic flows, and these methods can be used by the class controller 402in FIG. 18B.

Co-Existence of QoS-Enabled Traffic and Best-Effort Traffic

In may be desirable to integrate the proposed flow-VOQs and class-queueswith bounded buffer sizes and QoS guarantees into routers, along withthe existing Best-Effort Internet traffic. This concept is illustratesin FIG. 19A. Let the network distinguish between two types of traffic:‘QoS-enabled’ traffic which is periodically reshaped to have a boundedNSLL and is delivered with QoS guarantees, and regular ‘Best-Effort’(BE) internet traffic which does not have a bounded NSLL and isdelivered on a best-effort basis. For example, regular best-effortInternet traffic may use the bursty TCP flow-control protocol, so that atraffic flow does not have a bounded NSLL.

FIG. 19A illustrates an input port 12, where the buffers are logicallypartitioned into two types, buffers for QoS-enabled traffic and buffersfor regular Best-Effort Internet traffic. The router controller 20 a candistinguish between these two types of traffic on the network: theQoS-enabled traffic and the regular Best-Effort Internet traffic.

The QoS-enabled traffic may consist of a new DiffServ traffic class(i.e., a new EF class for traffic with a bounded NSLL). Trafficbelonging to this new QoS-enabled class is transmitted into the networkat the source node with a bounded NSLL (when viewed at the appropriatelevel of the network hierarchy). The QoS-enabled traffic may alsoconsist of a traffic flow which is transmitted into the network with abounded NSLL, and which has provisioned bandwidth along its path usingan RSVP-like control protocol. The QoS-enabled traffic may also consistof an MPLS traffic flow or an aggregated MPLS traffic flow which istransmitted into the network at the source node with a bounded NSLL, andwhich has provisioned bandwidth along its path using an MPLS-likecontrol protocol.

Incoming packets are processed by a controller 20 a, which controls ademultiplexer 15 a.

Module 500 contains all the VOQs 16 for QoS-enabled traffic. Module 502contains all the VOQs for existing Best-Effort Internet traffic. Thecontroller 20 a reads the packet header, and directs each incomingpacket to the appropriate module 500 for QoS-enabled traffic or module502 for Best-Effort traffic. Controller 20 a may also perform policingfunctions. Any packets which have excessively bursty trafficcharacteristics are forwarded to the Best-Effort module 502. Module 500has a controller 20 b,a demultiplexer 15 b to direct the packet into theappropriate class-based VOQ 16, and a VOQ server 18 b for QoS-enabledtraffic. Similarly, the Best-Effort module 502 has a controller 20 c, ademultiplexer 15 c to direct the packet into the appropriate best-effortVOQ 16, and a VOQ server 18 c for Best-Effort traffic. Thedemultiplexers 15 a, 15 b and 15 c are drawn as logically distinctentities, but they may be realized in fewer physical demultiplexers 15which logically perform the same functions. Similarly, the servers 18 a,18 b and 18 c are drawn as logically distinct entities, but they may berealized in fewer physical servers 18 which are logically perform thesame functions.

The servers 18 a, 18 b, 18 c can be controlled using the staticflow-scheduling methods described earlier, or the dynamic flowscheduling methods described earlier, with minor changes. If staticflow-scheduling methods are used, the schedules can be stored in thecontrollers 110 and re-used, until they are recomputed.

FIG. 19B illustrates the input port 12 from FIG. 19A, in more detail.The input port 12 in FIG. 19B consist of a controller 20 a and a server15 a. It also has several VOQ-modules 410 for QoS-enabled traffic. EachVOQ-module 410 is associated with one VOQ or output port and containsseveral class-VOQs 406 and flow-VOQs 106. The input port 12 also has acontroller 20 b and a demultiplexer 15 b for QoS-enabled traffic. Theinput port 12 also has a controller 20 c, a demultiplexer 15 c, andseveral VOQs 16 for best-effort traffic. It has a VOQ-server 18 b forQoS-enabled traffic, a VOQ-server 18 c for best-effort traffic, and aserver 18 a which may select a QoS-enabled VOQ or a best-effort VOQ forservice in one time-slot. The usual Best-Effort internet traffic,including the usual DiffServ traffic which has no guaranteed bound onthe NSLL, can be handled by the Best-Effort VOQs 16. QoS-enabled trafficflows, which request bounded buffer sizes and guaranteed QoS and whichhave a bounded NSLL, are handled by the VOQ-modules 410.

The router controller 20 a will distinguish between the two types oftraffic on the network: QoS-enabled traffic which is reshapedperiodically to have a bounded NSLL, and regular Best-Effort internettraffic which does not have a bounded NSLL. The QoS-enabled traffic mayconsist of a new DiffServ traffic class (i.e., a new EF class). Trafficbelonging to this new class is transmitted into the network at thesource node with a bounded NSLL (at an appropriate level of thehierarchical network). The QoS-enabled traffic may also consist of atraffic flow which is transmitted into the network with a bounded NSLL,and which has provisioned bandwidth along its path using an RSVP-likecontrol protocol. The QoS-enabled traffic may also consist of an MPLStraffic flow or an aggregated MPLS traffic flow which is transmittedinto the network at the source node with a bounded NSLL, and which hasprovisioned bandwidth along its path using an MPLS-like controlprotocol.

In FIG. 19B, arriving packets are processed by the controller 20 a,which examines the packet header to determine the appropriate outputport 14 and the type of service, i.e., QoS-enabled or Best-Effort.Packets belonging to a QoS-enabled traffic class or traffic flow with abounded NSLL can be forwarded to controller 20 b. Controller 20 b willcontrol the demultiplexer 15 b and direct the packet to the appropriateVOQ-module 410. Each VOQ-module 410 has several traffic-class-VOQs 406and several flow VOQs 106. Each traffic-class-VOQ 406 stores all thepackets belonging to one QoS-enabled traffic class. Each flow-VOQ 106stores all the packets belong to one QoS-enabled traffic flow or oneaggregated QoS-enabled traffic flow. The basic VOQs 16 will store allother best-effort packets, i.e., packets which are not QoS-enabled, orpackets which do not have a bounded NSLL.

In each time-slot, the IP-controller 110 a in an input port will enablethe VOQ-server 18 a to select either a VOQ-module 410 for service, or aregular best-effort VOQ 16 for service.

The control signals for the controller 110 a can be computed using thestatic flow scheduling methods of FIG. 9 or the dynamic flow-schedulingmethods of FIG. 10 (with excess bandwidth sharing disabled). Thesecontrol signals can be computed dynamically, or they can be precomputedfor a scheduling frame and re-used for subsequent scheduling frames,when the provisioned traffic rates between the input ports and outputports for QoS-enabled traffic flows do not change. When a VOQ-module 410receives service from the VOQ-server 18, the server 420 must select aclass-VOQ 406 or a flow-VOQ 106 for service.

The control signals for the server 420 can be computed using the staticscheduling methods of FIG. 9 or the dynamic scheduling methods of FIG.10. If the static methods are used, the schedules can be stored incontroller 421 and be reused, until they are recomputed. Each virtualqueues in VOQ-module 410 may have an associated rate, i.e., eachclass-VOQs 406 may have a rate, and each flow VOQs 106 may have a rate.These rates are expressed as time-slot reservations per schedulingframe, and the sum of all these rates must be <=F, which is the numberof time-slot reservations in an scheduling frame.

For example, the method Static Flow Schedule in FIG. 9A can be used tocompute the control signals for VOQ-servers 18 b and 18 c. The methodcan schedule traffic class-VOQs and traffic flow-VOQs together, ratherthan just traffic flows-VOQs alone. The method accepts 2 inputs, avector ‘rate’ and a vector ‘VOQS’. To compute a schedule for server 18b, let the incoming vector VOQS be a vector where VOQS(t)=1 indicatesthat the server 18 b is enabled for service in time-slot ‘t’. Let theinput vector ‘rate’ be the rates of the class-VOQs and the flow-VOQs.The vector FVOQS returned by the method in FIG. 9A will be a schedule,which identifies which class-VOQ 406 or which flow-VOQ 106 should beserved in time-slot ‘t’ (assuming the server 18 b is enabled intime-slot ‘t’). This schedule will have a bounded NSLL for eachclass-VOQ or flow-VOQ, since the traffic requirements of each VOQ arescheduled approximately evenly in each half of the scheduling frame, andthis property applies recursively. This schedule can therefore be usedto control the VOQ-server 18 b. The method Static Flow_Schedule RealTimein FIG. 9C can also be used to control the server 18 a to schedulebetween two types of traffic, QoS-enabled traffic or Best-Efforttraffic, for the special case where every time-slot is available forscheduling. The method Static_Flow_Schedule in FIG. 9A can also be usedto compute control signals for the server 18 c, to select a best-effortVOQ 16 for service when the best-effort server 18 c is enabled. Thedynamic flow-scheduling methods in FIGS. 10A and 10B can also be used toschedule servers 18 a, 18 b and 18 c. The excess bandwidth sharingproperty may be disabled, to minimize the NSLL.

Within a VOQ-module 410, here are several methods in which a server 420can select a packet for service, when it is enabled for service. Themethod Static Flow Schedule in FIG. 9A can be used to schedule allQoS-enabled traffic classes and traffic flows. The method can guaranteea bounded NSLL for QoS-enabled traffic classes leaving the routers andQoS-enabled flows leaving the router. Alternatively, the dynamicflow-scheduling methods in FIGS. 10A and 10B can be modified slightly toconsider both QoS-enabled traffic-class-VOQs 406 and flow-VOQs 106 andcan be used. (For dynamic flow-scheduling, the excess bandwidth sharingproperty may be disabled in some routers, to reshape the traffic andachieve a bounded NSLL).

The router controller 20 will forward all non-QoS-enabled traffic, ortraffic with inherently bursty traffic profiles, to the best-effort VOQs16, where it is handled as it is in the current Best-Effort Internetnetwork. The VOQs 16 are scheduled for service by a best-effortcontroller 110 c, which controls the best effort VOQ-server 18 c. Forexample, all existing Internet routers use heuristic best-effortschedulers for scheduling the transmissions of the best-effort VOQs.

The VOQ-modules 410 will require negligible buffer space in a router,compared to the basic best-effort VOQs 16. Theorems 1-4 and extensivesimulations indicate that a VOQ-module 410 can require a small fraction,i.e., 1% or less, of the amount of buffer space associated with abest-effort VOQ 16.

Other Embodiments Applications to CIXQ and CIOQ Switches

Referring to the Input queued switch 10 shown in FIG. 1A, theVOQ-transmission-schedules for the input ports 12 in FIG. 1A can becomputed using the method described in [18], which guarantees that eachVOQ 16 receives its requested service with a bounded NSLL, provided thatthe switch size N and the length of the scheduling frame F are bounded.The method in [18] can also be used to schedule the switches in FIGS.1B, 1C and 1D.

Other methods exist to schedule the switches in FIGS. 1B, 1C and 1Dwhile achieving bounded buffer sizes and strict QoS guarantees.According to Theorems 1-4 stated earlier, each of these switches willmaintain bounded queue sizes and achieve strict QoS guarantees for alltraffic flows, if the traffic at each class-VOQ or flow-VOQ arrives witha bounded NSLL<=K, if the traffic at each class-VOQ or flow-VOQ departswith a bounded NSLL<=K. According to Theorem 1, the class or flow-VOQsizes will be bounded. Therefore, it is desirable to explore alternativescheduling methods which achieve bounded NSLL.

FIG. 1B illustrates a CIXQ switch with input ports 12 and a switchingmatrix 32 which contains internal crosspoint queues 34. FIG. 1Cillustrates a CIIOQ switch with input ports 12 and a switching matrix32, which contains internal input queues 35 and internal output queues36.

The CIXQ switch in FIG. 1B can be made simpler to schedule, at theexpense of having larger (but bounded) buffers and queues within theswitching matrix 32. According to theorems 1-4, let each crosspointqueue 34 have a size of 2K or 4K packets. Let each input port 12transmit packets into the switching matrix 32 with a bounded NSLL=K, atany rate less than or equal to 100%, i.e., the links 31 from the inputport 12 to the switching matrix 32 can be partially or fully loaded. Ifthe internal crosspoint queues 34 are sufficiently large, i.e., have asize of 2K or 4K packets, then the computation of theVOQ-transmission-schedule can be simplified. Let the CIXQ switch have atraffic matrix T, which specifies the traffic between input ports 12 andoutput ports 14, as shown in FIG. 16A. This matrix can be configured byan autonomic controller, or by the system administrator. Each row j ofthe matrix T, for 1<=j<=N, can be processed to yield aVOQ-transmission-schedule for input port j, which guarantees a boundedsize for the VOQ. There are 2 methods for processing the row j of thematrix. The first method is a Static-VOQ scheduling method. The methodStatic_Flow_Schedule RealTime in FIG. 9C can be used to schedule VOQsinstead of individual traffic-flows, for the special case when everytime-slot is available for scheduling. The method accepts 2 inputs, avector ‘rate’ and a vector ‘VOQS’. Let the incoming vector VOQS be avector of all 1s, indicating that all time-slots in the scheduling frameare available to be used. Let the input vector ‘rate’ be the row j ofthe matrix T. The vector FVOQS returned by the method in FIG. 9A will bea VOQ-transmission-schedule, which identifies which VOQ should be servedin which time-slot. This VOQ-transmission-schedule will have a boundedNSLL for each VOQ, since the traffic requirements of each VOQ arescheduled approximately evenly in each half of the scheduling frame, andthis property applies recursively. This VOQ-transmission-schedule can beused in the input port 12, to control the VOQ-server 18. The methodStatic Flow Schedule in FIG. 9A can also be used to schedule the flowswithin each VOQ, or the traffic classes within each VOQ, as describedearlier. Therefore, the CIXQ switch can be scheduled to achieve boundedbuffer sizes and strict QoS guarantees for every class-VOQ or flow-VOQ,sharing a VOQ.

The CIIOQ switch in FIG. 10 can also be simpler to schedule relative tothe pure IQ switch in FIG. 1A, at the expense of having larger (butbounded) buffers and queues. The CIIOQ switch in FIG. 10 can usesufficiently large internal input queues 35 in the switching matrix, andsufficiently large internal output queues 36 in the switching matrix.According to theorems 1-4, let each internal input queue 35 or internaloutput queue 36 have a size of approx. 2K or 4K packets. Let each inputport 12 transmit packets from the class-VOQs or the flow-VOQs with abounded NSLL, at any rate less than or equal to 100%, i.e., the links 31from the input port 12 to the switching matrix 32 can be fully loaded.

The method Static Flow_Schedule RealTime in FIG. 9C can be used tocompute a VOQ-transmission-schedule for the CIIOQ switch, in the samemanner it was used for the CIXQ switch. The same method Static FlowSchedule in FIG. 9A can also be used to schedule the flows within eachVOQ, or the traffic classes within each VOQ, as described earlier.Therefore, the CIIOQ switch can be scheduled to achieve bounded buffersizes and strict QoS guarantees for every class-VOQ or flow-VOQ, sharinga VOQ, using static scheduling algorithms.

The above methods compute static schedules, which are valid as long asthe traffic rates in the traffic rate matrix remain constant. Inpractice, in a backbone router these traffic rates may changeperiodically, perhaps 100 times a second, so the schedules must berecomputed at this rate. The static transmission-schedules may be storedand re-used for subsequent frames, until they are recomputed.

The CIXQ switch and the CIIOQ switch can also be scheduled using themethods to dynamically schedule traffic flows, as shown in FIGS. 10A and10B. For example, the methods Dynamic_Add_Packet and Dynamic_Rem_Packetcan be modified and used, with the bandwidth sharing option disabled.Every time a packet arrives for a traffic-class-VOQ or a flow-VOQ, themethod Dynamic_Add_Packet is used to assign a VFT. In each time-slot,the method Dynamic_Remove_Packet can be used to identify a class-VOQ ora flow-VOQ for service within a VOQ. The same dynamic scheduling methodscan be modified and can also be used to schedule the VOQs, using aVOQ-server 18. Therefore, the CIIOQ switch can be scheduled to achievebounded buffer sizes and QoS guarantees for class-VOQs or flow-VOQssharing a VOQ, using dynamic scheduling algorithms.

In a one-level Dynamic scheduling method, the method Dynamic_Add_Packetof FIG. 10A and Dynamic_Remove_Packet of FIG. 10B can be used to add andremove packets from each input port, where all VOQs within one inputport are no longer differentiated. The excess bandwidth sharing featureshould be disabled, so ensure that the traffic is transmitted with abounded NSLL. In a two-level Dynamic scheduling method, the methodDynamic_Add_Packet of FIG. 10A and Dynamic_Remove_Packet of FIG. 10B canbe used add and remove packets from each VOQ. A first server selects theVOQ to service using server 18, and a second server selects the flowwithin the to service, as described earlier.

In a CIXQ switch, each column server 37 in the switching matrix 32 canbe scheduled using the methods of FIG. 9 or 10, or any other heuristicalgorithm such a Random-Selection, Longest-Queue-First, orOldest-Cell-First, etc. When the methods of FIGS. 9 and 10 are used,then according to theorems 1-4 stated earlier, the sizes of theflow-VOQs 106 and the XQs 34 will remain small and bounded. When othermethods such as Oldest-Cell-First are used, then according to extensivesimulations, the sizes of the flow-VOQs 106 and the XQs 34 will remainsmall and statistically bounded.

All-Optical Networks

All optical networks typically buffer optical packets in fiber loops.Typically, each nanosecond of transmitted optical data occupies about0.2 meters of fiber. At a 40 Gbps transmission rate, a packet with 1000bytes will hold approx. 8000 bits which requires 200 nanoseconds totransmit. Therefore, a fiber loop buffer for an optical packet requiresabout 40 meters of fiber. It is desirable to minimize the number ofoptical packet buffers in an optical packet switch. All optical networksshould transmit provisioned traffic flows with the smallest possibleNSLL, and each switch should use a non-work-conserving flow-scheduler tomaintain a very small and bounded NSLL.

To minimize the amount of buffering, an optical switch can use an IQswitch design as shown in FIG. 1A. According to the data in FIG. 12, anoptical switch can be designed with approximately 2 optical packetbuffers per provisioned traffic flow per optical packet-switch. Trafficaggregation and traffic classification could be used, to limit theamount of buffering. The Static-Flow-Scheduling scheduling method inFIG. 9A can be implemented in an electronic processor, to compute aflow-transmission-schedule for each input port. This schedule can bestored and used to control the optical buffers, so that every class-VOQor flow-VOQ achieves a bounded NSLL and bounded buffer sizes.

Wireless Mesh Networks

It has been shown that the problem of scheduling traffic in aninfrastructure wireless mesh network can be transformed to the problemof scheduling traffic in an IQ switch as shown in FIG. 1A. In the paper[24] by T. H. Szymanski entitled “A Conflict-Free, Low-JitterGuaranteed-Rate MAC Protocol for Base-Station Communications in WirelessMesh Networks”, Proc. First Int. Conference on Access Networks, LasVegas, October 2008, a schedule computed for IQ switches can betransformed to a schedule for a multi-hop wireless mesh network. In thetransformation, the Input ports of the IQ switch become the output portsof a wireless router in the wireless mesh network. Wireless mesh routershave a unique property that the router typically only receives onepacket per time-slot over its wireless radio. Therefore, by followingthe transformation methodology described in the paper [24], schedulescomputed for an IQ switch can be transformed to schedules for a wirelessmesh network.

The static flow scheduling method in FIG. 9A can be implemented in anelectronic processor, to compute a flow-transmission-schedule for eachwireless router. These schedules can be stored and used to control thewireless router. The dynamic flow-scheduling method in FIG. 10 can beused to compute a flow-transmission-schedule for each wireless router.These schedules can be stored and used to control the wireless router,so that every class-VOQ or flow-VOQ achieves a bounded NSLL, boundedbuffer sizes and QoS guarantees.

SUMMARY

Of course, the above described embodiments are intended to beillustrative only and in no way limiting. The described embodiments ofcarrying out the invention are susceptible to many modifications ofform, arrangement of parts, details and order of operation. Theinvention, rather, is intended to encompass all such modificationswithin its scope, as defined by the claims.

For example, the buffers and queues in the routers have been describedas flow-VOQs, VOQs, class-VOQs, etc. In practice, all these queues mayreside in the same memory and may be defined through pointers to memory,and they may exist only as logical abstractions. In the CIXQ switch, themultiple VOQs in each input port are technically not required, as theycould be collapsed into one large virtual queue which contains allpackets arriving at one input port. This variation is easily handledwith the proposed methods.

1. (canceled)
 2. A switch for switching a plurality of guaranteed-rate(GR) traffic flows over a set of output ports, given a scheduling framecomprising F time-slots for integer F, comprising: N input ports forreceiving packets and M output ports for transmitting packets, forintegers N and M; a plurality of queues, wherein each queue bufferspackets which arrive at a common one of said N input ports and whichdepart on a common one of said M output ports; wherein each GR trafficflow is associated with a guaranteed data-rate requirement, wherein eachGR traffic flow is associated with one queue, and wherein packetsassociated with a GR traffic flow are buffered in its associated queue;memory for storing a flow-schedule, wherein the flow-schedule determineswhich of the GR traffic flows associated with said queues, if any, havea reservation to transmit in each time-slot in said scheduling frame;wherein the flow-schedule provides each of said GR traffic flows with aguaranteed number of time-slot reservations per scheduling framesufficient to meet its guaranteed data-rate requirement, and wherein foreach GR traffic flow with a guaranteed data-rate requirement whichexceeds one packet transmission per scheduling frame, said flow-scheduleprovides said GR traffic flow with a substantially equal number oftime-slot reservations for transmission in each half of the schedulingframe with a substantially equal size.
 3. The switch of claim 2, whereinthe flow-schedule provides each of said GR traffic flows with asubstantially pro-rated number of time-slot reservations fortransmission in a subset of the scheduling frame comprising time-slots
 1. . . E for integer E, where 1<=E<=F.
 4. The switch of claim 2, whereinthe memory is distributed throughout the switch.
 5. The switch of claim2, wherein the GR traffic flows belong to a traffic class in theDifferentiated Services service model.
 6. The switch of claim 2, furthercomprising a traffic-shaper module, comprising a controller, memory tobuffer packets, memory to buffer tokens, and a token-generator, whereinsaid traffic-shaper module is operable to buffer incoming packetsassociated with a GR traffic flow, and release said packets in a mannerto reduce the burstiness of said GR traffic flow.
 7. The switch of claim2, wherein each of said queues is partitioned into a plurality offlow-queues, and wherein each flow-queue buffers packets associated withone GR traffic flow.
 8. The switch of claim 3, wherein each of saidqueues is partitioned into a plurality of flow-queues, and wherein eachflow-queue buffers data associated with one GR traffic flow.
 9. Theswitch of claim 2, further comprising memory for storing aqueue-schedule, wherein each of said plurality of queues is associatedwith a guaranteed data-rate requirement, wherein said queue-scheduledetermines which of said queues, if any, have a reservation to transmitin each time-slot of said scheduling frame, and wherein saidqueue-schedule provides each of said queues with a guaranteed number oftime-slot reservations per scheduling frame sufficient to satisfy itsguaranteed data-rate requirement.
 10. The switch of claim 9, wherein foreach queue with a guaranteed data-rate requirement which exceeds onepacket transmission per scheduling frame, said queue-schedule providessaid queue with a substantially equal number of time-slot reservationsfor transmission in each half of the scheduling frame with asubstantially equal size.
 11. The switch of claim 10, wherein thequeue-schedule provides each queue with a substantially pro-rated numberof time-slot reservations for transmission in a subset of saidscheduling frame comprising time-slots 1 E for integer E, where 1<=E<=F.12. The switch of claim 2 which also switches a plurality of class-based(CB) traffic flows over a set of output ports, comprising a plurality ofclass-queues, wherein each class-queue is associated with a guaranteeddata-rate requirement, wherein each class-queue buffers packets whicharrive at a common one of said N input ports and depart on a common oneof said M output ports, wherein a plurality of CB traffic flows isassociated with each class-queue, and wherein packets associated with aCB traffic flow are buffered in its associated class-queue; wherein aclass-queue can transmit in the time-slots when a corresponding queue isnot transmitting.
 13. The switch of claim 12, further comprising memoryto store a class-schedule, wherein each class-queue is associated with aguaranteed data-rate requirement, wherein said class-schedule determineswhich of said class-queues, if any, has a reservation to transmit ineach time-slot in said scheduling frame; and wherein said class-scheduleprovides each of said class-queues with a guaranteed number of time-slotreservations in a scheduling frame sufficient to meet its guaranteeddata-rate requirement.
 14. The switch of claim 13, wherein for eachclass-queue with a guaranteed data-rate requirement which exceeds onepacket transmission per scheduling frame, said class-schedule provideseach of said class-queues with a substantially equal number of time-slotreservations for transmission in each half of the scheduling frame witha substantially equal size.
 15. The switch of claim 14, wherein saidclass-schedule provides each of said class-queues with a substantiallypro-rated number of time-slot reservations for transmission in a subsetof the scheduling frame comprising time-slots 1 . . . E for integer E,where 1<=E<=F.
 16. The switch of claim 13, wherein the CB traffic flowsbelong to a traffic class in the Differentiated Services service model.17. The switch of claim 11, further associated with ascheduling-processor, wherein said scheduling-processor will process thecontents of a class-queue, to determine which of the packets bufferedwithin said class-queue is selected to transmit next.
 18. The switch ofclaim 17, wherein said scheduling-processor selects the oldest packet inthe class-queue to transmit next.
 19. The switch of claim 2 which alsoswitches a plurality of Best-Effort (BE) traffic flows over a set ofoutput ports, comprising a plurality of BE-queues, wherein each BE-queuebuffers packets which arrive at a common one of said N input ports anddepart on a common one of said M output ports, wherein a plurality ofzero or more BE traffic flows is associated with each BE-queue, andwherein packets associated with a BE traffic flow are buffered in itsassociated BE-queue; wherein a BE-queue can transmit in the time-slotswhen a corresponding queue is not transmitting.
 20. The switch of claim12 which also switches a plurality of Best-Effort (BE) traffic flowsover a set of output ports, comprising a plurality of BE-queues, whereineach BE-queue buffers packets which arrive at a common one of said Ninput ports and depart on a common one of said M output ports, wherein aplurality of zero or more BE traffic flows is associated with eachBE-queue, and wherein packets associated with a BE traffic flow arebuffered in its associated BE-queue; wherein a BE-queue can transmit inthe time-slots when a corresponding queue is not transmitting, and whena corresponding class-queue is not transmitting.
 21. A packet-switchednetwork to deliver a plurality of guaranteed rate (GR) traffic flowsthrough a plurality of switches, wherein each of said plurality of GRtraffic flows originates at a source node, terminates at a destinationnode, and traverses a fixed path of intermediate switches between itssource node and its destination node, and wherein each GR traffic flowis associated with a guaranteed data-rate requirement; said networkcomprising a plurality of J switches for integer J, wherein saidswitches satisfy the requirements of claim
 2. 22. The network of claim21, wherein for each switch, the schedule for said switch provides eachflow-queue within said switch with a substantially pro-rated number oftime-slot reservations for transmission in a subset of the schedulingframe comprising time-slots 1 . . . E for integer E, where 1<=E<=F,wherein F is the length of the scheduling-frame for said switch.
 23. Thenetwork of claim 21, wherein the memory within each switch isdistributed throughout the switch.
 24. The network of claim 21, whereinthe GR traffic flows belong to a traffic class in the DifferentiatedServices service model.
 25. The network of claim 21, wherein each switchfurther satisfies the requirements of claim 10 (to comprisequeue-schedules).
 26. The network of claim 25, wherein each switchfurther satisfies the requirements of claim 11 (to comprisequeue-schedules with pro-rated transmission).
 27. The network of claim21, wherein each switch further satisfies the requirements of claim 14(to comprise class-queues).
 28. The network of claim 27, wherein eachswitch further satisfies the requirements of claim 15 (to compriseclass-queues with pro-rated transmission).
 29. The network of claim 21,wherein at least one of said plurality of GR traffic flows is associatedwith a plurality of fixed paths between its source node and itsdestination node, wherein each fixed path comprises a plurality ofintermediate switches, and wherein each fixed path in said plurality offixed paths is associated with a guaranteed data-rate requirement. 30.The network of claim 21, wherein a source node of at least one of saidGR traffic flows comprises a traffic shaper module, wherein saidtraffic-shaper module comprises a controller, memory to buffer packets,memory to buffer tokens, and a token-generator, wherein saidtraffic-shaper module is operable to buffer packets associated with saidGR traffic flow, and release said packets for transmission along a fixedpath with a relatively constant rate of transmission.